% Converted from Microsoft Word to LaTeX
% by Chikrii Softlab Word2TeX converter (version 5.0)
% Copyright (C) 1999-2011 Chikrii Softlab. All rights reserved.
% http://www.chikrii.com
% mailto: support@chikrii.com
% License: CSL#005E58

%\documentclass[twoside]{article}
%\usepackage{epsfig,html,amsmath,amssymb,lscape,longtable,pstricks,cite,hyperref}
%\usepackage{graphics}
%\pagestyle{headings}
%\markboth{}{}
%\newcommand{\hytt}[1]{\texttt{\hyphenchar\font=\defaulthyphenchar #1}}

% !Mode:: "TeX:UTF-8"
\documentclass[twoside]{article}
\usepackage{latexsym}

\usepackage{epsfig,html,amsmath,longtable,cite,hyperref}
\usepackage{geometry}
\usepackage{graphics}
\usepackage{graphicx}
\usepackage{color}
\usepackage{subfig}
\usepackage{indentfirst}
\usepackage{multicol}
\usepackage{listings}
\usepackage{lipsum}

\usepackage{xeCJK} % seperate the english and chinese

\setCJKmainfont[ItalicFont={AR PL UKai CN}]{AR PL UMing CN} %????????
%\XeTeXlinebreaklocale "zh"  % Auto linebreak for chinese
\XeTeXlinebreakskip = 0pt plus 1pt minus 0.1pt % Auto linebreak for chinese

\setlength{\parindent}{2em}
\hypersetup{urlbordercolor=0 0 0,pdfborder=0 0 1 [3 2]}

\begin{document}
	
	%\linebreak {4}
	
	%{\kaishu ??}
	%{\heiti ??}
	%{\fangsong ??}
	
	\title{PDMS PARAGON Reference Manual\\Version 11.6SP1}
	\author{
	}
	\maketitle {}
	
	\begin{figure}[htbp]
		\centerline
		\includegraphics[width=4.63cm]{Paragon1}
		\label{fig1}
	\end{figure}
	
	\thispagestyle{empty}%????????
	\newpage
	\setcounter{page}{1}%????????
	%\begin{multicols}{2}
	\numberwithin{equation}{subsection}
	
	
	\tableofcontents
	\newpage
	
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.88cm]{Paragon2}}
		\label{fig2}
	\end{figure}
	
	\textbf{pdms1161/Paragon Reference Manual Issue 280605}
	
	This manual provides documentation relating to products to which you may not 
	have access or which may not be licensed to you. For further information on 
	which Products are licensed to you please refer to your licence conditions.
	
	$\heartsuit $ \textbf{Copyright 1991 through 2005 AVEVA Solutions Limited}
	
	All rights reserved. No part of this document may be reproduced, stored in a 
	retrieval system or transmitted, in any form or by any means, electronic, 
	mechanical, photocopying, recording or otherwise, without prior written 
	permission of AVEVA Solutions.
	
	The software programs described in this document are confidential 
	information and proprietary products of AVEVA Solutions or its licensors.
	
	\underline {http://www.aveva.com}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.42in,height=2.37in]{Paragon3}}
		\label{fig3}
	\end{figure}
	
	AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
	
	\section{Revision History}
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{72pt}|l|l|}
				\hline
				\textbf{Date}& 
				\textbf{Version}& 
				\textbf{Notes} \\
				\hline
				Oct 03& 
				11.5& 
				Format change and minor text changes. \\
				\hline
				August 04& 
				11.6& 
				Miscellaneous updates for 11.6. \\
				\hline
				June 05& 
				11.6.SP1& 
				Minor changes and corrections. \\
				\hline
			\end{tabular}
			\label{tab1}
		\end{center}
	\end{table}
	
	Revision-History-ii VANTAGE PDMS PARAGON
	

	
	\section{Introducing PARAGON}
	\label{sec:introducing}
	\subsection{What Does PARAGON Do?}
	\label{subsubsec:mylabel1}
	PARAGON enables you to generate or modify a PDMS Catalogue, with facilities 
	for constructing Catalogue Components under fully interactive visual 
	control, including 3D colour-shaded representations of the items being 
	designed.
	
	PARAGON combines aspects of both catalogue creation and model design 
	functionality within a single module. This means that a catalogue designer 
	not only has write access to a project's Catalogue databases, but may also 
	read data from the Design databases. If given write access, the catalogue 
	designer could also experiment with new catalogue component configurations 
	in a trial design database. This approach simplifies catalogue maintenance 
	and design. Similarly, it is often useful for a plant design engineer to 
	have access to the Catalogue to query details of specific components.
	
	PARAGON has a Graphical User Interface consisting of forms and menus. The 
	interface provides access to the most commonly used facilities. To enter 
	direct command syntax, use the \textbf{Display\textgreater Command Line 
	}menu option to open a special window which accepts command inputs and 
	displays system outputs. Full details of using PARAGON's menus and forms are 
	given in the on-line help, and how to design your own graphical user 
	interface is explained in the \textit{Plant Design Software Customisation Guide}.
	
	\subsection{About this Manual}
	\label{subsubsec:about}
	This document is a \textbf{Reference Manual }for PARAGON. It describes all 
	of the PARAGON keyboard-entered commands in detail. If you need information 
	on how to use PARAGON to carry out the principal Catalogue design activities 
	with minimal use of the keyboard, by using the graphical Forms and Menus 
	interface, refer to the on-line help for the PARAGON applications.
	
	It is assumed that you have attended a PDMS training course and are familiar 
	with the basic concepts underlying the use of PDMS.
	
	\textbf{NOTE: }The PARAGON and DESIGN modules share a common command syntax, 
	but differ in that PARAGON operates on a Catalogue database while DESIGN 
	operates on a Design database. Only the Catalogue construction commands are 
	explained in this manual; for details of commands for 3D design work, see 
	the \textit{PDMS DESIGN Reference Manual}.
	
	\subsubsection{1.2.1 Manual Structure}
	\label{para:mylabel1}
	\begin{enumerate}
		\item[\textbullet] Chapter 2 describes how to enter commands and the notation used to describe commands.
		\item[\textbullet] Chapter 3 describes how to enter and leave PARAGON and explains some general facilities.
		\item[\textbullet] Chapter 4 gives details of the Catalogue database hierarchy and the ways in which its constituent elements are defined.
		\item[\textbullet] Chapter 5 describes the ways in which you can navigate to any given element within the Catalogue database.
		\item[\textbullet] Chapter 6 introduces the principles of catalogue component design and their representation in graphical displays.
		\item[\textbullet] Chapter 7 gives details of the various types of point set (p-points and p-lines) and geometry sets (positive and negative 3D and 2D primitives) which are used in the design of catalogue components.
		\item[\textbullet] Chapter 8 explains the procedures for defining the various types of element which represent the design components within the Catalogue database.
		\item[\textbullet] Chapter 9 describes how to use PARAGON to define descriptive texts, connection compatibility tables, bolting tables and units of measurement associated with the catalogue components.
		\item[\textbullet] Chapter 10 explains the concept of datasets, used to store catalogue data which needs to be queried from DESIGN or DRAFT and which is not accessible by other means.
		\item[\textbullet] Chapter 11 describes how you can check the Catalogue database for inconsistencies from within PARAGON, so that errors can be corrected before the data is used a design.
		\item[\textbullet] Appendix A summarises some p-point conventions which should be followed to ensure the correct functioning of ISODRAFT.
		\item[\textbullet] Appendix B explains the advantages of using logical naming conventions to ensure reliable cross-referencing and the correct functioning of ISODRAFT.
		\item[\textbullet] Appendix C lists some sample macros for the design of typical piping components in the Catalogue database.
		\item[\textbullet] Appendix D contains a glossary of the element types relevant in PARAGON, grouped according to their function.
		\begin{itemize}
			\item The manual concludes with an Index.
			\begin{enumerate}
				\item \textbf{Communicating with PARAGON}
			\end{enumerate}
		\end{itemize}
	\end{enumerate}
	
	\subsection{Commands}
	\label{subsubsec:commands}
	This section describes the conventions used in this manual to describe 
	commands to be typed in from the keyboard. The description of each command 
	follows a standard format which is designed to allow the basic attributes of 
	a command to be interpreted easily. To get the best out of this manual, you 
	are strongly urged to read this section thoroughly.
	
	\subsubsection{Command Description Format}
	\label{para:command}
	Once you have located the required command in this manual, you will find 
	that it is described in a standard format. This format is described below.
	
	\begin{itemize}
		\item \textbf{Title }(e.g. \textbf{Setting Level Representation})
		\begin{itemize}
			\item \textbf{Keywords }This is a list of those PARAGON command words which are the prime constituents of the command syntax which carries out the given function.
			\item \textbf{Description }This is a brief description of the use of the command.
			\item \textbf{Example(s) }These are examples of typical command lines that show the effect of the principal options. Special notes on the behaviour of the command in specific conditions are given here.
			\item \textbf{Command Syntax }This shows the actual command with its possible options. The notation used for commands is described below (Section 2.1.2).
		\end{itemize}
		\item \textbf{Querying }The relevant querying options are listed.
	\end{itemize}
	
	\subsubsection{Syntax Diagrams}
	\label{para:syntax}
	The commands described in this manual have their legal command and 
	interrogation options presented in the form of \textbf{syntax diagrams}. 
	These diagrams formalise the precise command sequences which may be used and 
	are intended to supplement the explanations given in the appropriate 
	sections of the manual.
	
	The following conventions apply to syntax diagrams:
	
	\begin{itemize}
		\item All diagrams have abbreviated \textbf{names}. Such names are composed of lowercase letters enclosed in angled brackets, e.g. \textless expres\textgreater . These short names, which are
	\end{itemize}
	
	used for cross-referencing purposes in the text and within other syntax 
	diagrams, are supplemented by fuller descriptions where they are not 
	self-explanatory.
	
	\begin{itemize}
		\item \textbf{Commands }to be input from the terminal are shown in a combination of uppercase and lowercase letters. In general, these commands can be abbreviated; the capital letters indicate the \textbf{minimum permissible abbreviation}.
	\end{itemize}
	
	\textbf{NOTE: }This convention does \textit{not }mean that the second part of the command 
	must be typed in lowercase letters; commands may be entered in any 
	combination of uppercase and lowercase letters.
	
	For example, the command
	
	\textsf{DEFault}
	
	may be input in any of the following forms:
	
	\textsf{DEF DEFA DEFAU DEFAUL DEFAULT}
	
	Commands shown \textit{wholly }in uppercase letters cannot be abbreviated.
	
	\begin{itemize}
		\item Syntax diagrams are generally read from top left to bottom right.
		\item Points marked with a plus sign ($+)$ are \textbf{option junctions }which allow you to input any \textit{one }of the commands to the right of the junction. Thus
	\end{itemize}
	
	\begin{flushright}
		\textsf{\textgreater ---}$+$\textsf{--- ABC }-----.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar --- PQR \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar --- \textless dia\textgreater \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-------------}$+$\textsf{---\textgreater }
	
	means you may type in \textsf{\textbf{ABC }}\textit{or }\textsf{\textbf{PQR }}\textit{or }any 
	command allowed by the syntax given in diagram \textless dia\textgreater \textit{or }just 
	press Enter/Return to get the default option.
	
	\begin{itemize}
		\item Points marked with an asterisk (*) are \textbf{loop-back junctions}. Command options following these may be repeated as required. Thus
	\end{itemize}
	
	\begin{flushright}
		\textsf{.------\textless ------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater ---*--- option1 \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar --- option2 \textbar }
	\end{flushright}
	
	\textsf{\textbar \textbar }
	
	\textsf{`--- option3 ---}$+$ \textsf{\textgreater }
	
	permits any combination of option1 \textit{and/or }option2 \textit{and/or }option3 (each separated by at 
	least one space) to be used. The `options' may define commands, other syntax
	
	diagrams, or command arguments). The loop-back construction may form an 
	exception to the rule of reading from top left to bottom right.
	
	The simplified format
	
	\begin{flushright}
		\textsf{.----\textless -----.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\textsf{\textgreater ---*--- }\textsf{\textit{name 
	}}\textsf{---}$+$\textsf{---\textgreater }
	
	means that you may type in a list of PDMS names, separated by at least one 
	space.
	
	\subsubsection{Standard Command Tools}
	\label{para:standard}
	\textit{Command Tool }is a generic term covering command \textbf{arguments }(or \textbf{atoms}) 
	and command \textbf{parts}. Both classes of command tool fit into ordinary 
	commands and provide different ways of stating a particular requirement. 
	Command tools may be PDMS-wide or module-specific. This section describes 
	the standard Command Tools that may be used in PARAGON. They may be one of 
	the following:
	
	\begin{itemize}
		\item Standard Command Tools - which fit into ordinary commands
		\item External Macro Facilities - which can be used in a stored macro file and which control the behaviour of the macro when it is executed
		\item Standard Concepts - which apply globally within PARAGON
	\end{itemize}
	
	Some of the main command tools (or the PARAGON variations of them) 
	summarised for convenience:
	
	\begin{itemize}
		\item \textbf{Command Arguments}
	\end{itemize}
	
	Command arguments are also called \textbf{atoms }because they cannot be 
	broken down any further. They are individual units which PARAGON can 
	recognise as constituents of a complete command. They usually need to be 
	separated by spaces so that they are individually distinguishable. Command 
	arguments are distinguished from the other command parts by being written in 
	lower case italics. The principal command arguments are:
	
	\textsf{\textit{integer }}a positive or negative whole number, e.g. 2 -5 25
	
	\textsf{\textit{value }}a signed number with or without a decimal point, 
	e.g. 2.5 5 -3.8
	
	\textsf{\textit{letter }}a single alphabetic character
	
	\textsf{\textit{word }}a sequence of up to four letters with significance to 
	PDMS
	
	\textsf{\textit{text }}a string of alphanumeric or symbol characters, which 
	may include spaces, enclosed between single closing quotation marks '...' or 
	\textbar ...\textbar characters. This is normally used to add descriptive 
	material to an appropriate attribute. For example, DUTY 'Low Pressure'. 
	(Note that paired quotation marks `...' will not work.)
	
	\textsf{\textit{space }}the space bar (not usually specified unless of 
	special significance)
	
	\textsf{\textit{name }}a sequence of characters preceded by a / character 
	and representing a PDMS Element name, e.g. /VALVE1.
	
	\textsf{\textit{filename }}an external file name of the format 
	\textsf{/}\textit{filename}
	
	\textsf{\textit{varid }}an identifier (for use with the \textbf{VARIABLE 
	}command within macros) of the format !name, where `name' is a text string. 
	For example: \textsf{!COUNTER}
	
	\textsf{!height}
	
	\textsf{\textit{comma }}the , character, which can be used to concatenate 
	PARAGON commands; for example: \textsf{NEW UNIT, BUNI INCH, DUNI FINC}
	
	\textsf{\textit{plus minus }}the $+$, -, * and / characters, which can be 
	used within
	
	\textsf{\textit{star solid }}expressions, for example: \textsf{(1 
	}$+$\textsf{ 2), (1 - 2), (1 * 2), (1 / 2)}
	
	(Note that there must be a space before and after each of these command 
	arguments.)
	
	\begin{itemize}
		\item \textbf{Command Parts}
	\end{itemize}
	
	Command parts are subsets of the general command syntax which are used 
	frequently within other command sequences. The following command parts are 
	summarised here:
	
	\textbf{Expressions}
	
	Any mathematical, logical or alphabetical expression whose result replaces 
	it in the command syntax.
	
	\textbf{Dimensions}
	
	A physical dimension entered using default or explicit units.
	
	\textbf{Catalogue Element Types}
	
	A word used to represent a specific type of element in the Catalogue 
	database hierarchy.
	
	\textbf{Element Identifiers}
	
	Methods for specifying which database element you want your next commend to 
	act upon.
	
	\textbf{Cursor-picking Identifier }(\textless sgid\textgreater )
	
	This command part defines the most general method of identifying an Element. 
	The command is completed by picking an element using the cursor in a 
	graphical view.
	
	\begin{itemize}
		\item \textbf{Expressions }(\textless eval\textgreater )
	\end{itemize}
	
	If a value given within a command needs to be calculated from other known 
	values, you can enter an expression from which the required result is to be 
	evaluated by PARAGON as it executes the command. Such an expression must be 
	enclosed between parentheses (...) to identify where it begins and ends.
	
	Full details of the expression syntax are given in the \textit{Plant Design Software Customisation Guide }and \textit{Plant Design Software Customisation Reference Manual, }and are also 
	available as on--line help.
	
	\begin{itemize}
		\item \textbf{Dimensions }(\textless uval\textgreater )
	\end{itemize}
	
	Once the working units have been specified, all dimensions input 
	subsequently will be assumed to be in those units unless you override them. 
	(Note that these are simply specific examples of the use of `real' 
	expressions. You can include explicit units of measurement when entering a 
	value in \textit{any }expression.)
	
	\textbf{Examples}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{67pt}|l|l|}
				\hline
				\textsf{5}& 
				\textsf{5}& 
				\textsf{in current working units} \\
				\hline
				\textsf{5.5 EX 3}& 
				\textsf{5500}& 
				\textsf{in current working units} \\
				\hline
				\textsf{5.3/4}& 
				\textsf{5.75}& 
				\textsf{in current working units} \\
				\hline
				\textsf{5'}& 
				\textsf{5 feet}& 
				\textsf{(only use when working units are FINCH)} \\
				\hline
				\textsf{5'6}& 
				\textsf{5 feet 6 inches}& 
				\textsf{(only use when working units are FINCH)} \\
				\hline
				\textsf{5'6.3/4}& 
				\textsf{5 feet 6.75 inches}& 
				\textsf{(only use when working units are FINCH)} \\
				\hline
				\textsf{5 INCHES}& 
				\textsf{5 inches}& 
				\textsf{(regardless of current working units)} \\
				\hline
				\textsf{5 M}& 
				\textsf{5 metres}& 
				\textsf{(regardless of current working units)} \\
				\hline
				\textsf{5'6.3/4 IN}& 
				\textsf{5 feet 6.75 inches}& 
				\textsf{(regardless of current working units)} \\
				\hline
			\end{tabular}
			\label{tab2}
		\end{center}
	\end{table}
	
	\textbf{NOTE: }On output, values are rounded by default as follows:
	
	\begin{itemize}
		\item millimetres to the nearest millimetre
		\item inches to the nearest 1/32 or 0.1 inch.
	\end{itemize}
	However, rounding on output may be controlled by using the \textbf{PRECISION 
	}command. Within PARAGON, values are stored as accurately as the host 
	computer will allow.
	
	\begin{itemize}
		\item \textbf{Catalogue Element Types }(\textless snoun\textgreater )
	\end{itemize}
	
	This command part refers to an element type in the Catalogue hierarchy.
	
	\textbf{Catalogue administrative elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|l|}
				\hline
				\textsf{WORLd}& 
				\textsf{CATAlogue}& 
				\textsf{SECTion}& 
				\textsf{STSEction} \\
				\hline
				\textsf{CATEgory}& 
				\textsf{STCAtegory}& 
				\textsf{TEXT}& 
				\\
				\hline
			\end{tabular}
			\label{tab3}
		\end{center}
	\end{table}
	
	\textbf{Piping Components:}
	
	\textsf{SCOMponent COMPonent }\textsf{\textit{number}}
	
	\textbf{Profile Components:}
	
	\textsf{SPRFile PROFile }\textsf{\textit{number}}
	
	\textbf{Joint Components:}
	
	\textsf{SJOInt JOINt }\textsf{\textit{number}}
	
	\textbf{Fitting Components:}
	
	\textsf{SFITting}
	
	(\textbf{NOTE}: \textsf{FITTing }\textsf{\textit{number }}is \textbf{not }a 
	valid option)
	
	\textbf{3D Geomset elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{77pt}|p{75pt}|p{102pt}|p{71pt}|}
				\hline
				\textsf{GMSEt} \par \textsf{SCOne}& 
				\textsf{SBOX} \par \textsf{LSNout}& 
				\textsf{SDIsc} \par \textsf{SDSH}& 
				\textsf{SDIsk} \par \textsf{BOXIng} \\
				\hline
				\textsf{SSLCylinder}& 
				\textsf{SSPHere}& 
				\textsf{LCYLinder}& 
				\textsf{SCYLinder} \\
				\hline
				\textsf{LINes}& 
				\textsf{SCTorus}& 
				\textsf{SREVolution}& 
				\textsf{SRTorus} \\
				\hline
				\textsf{TUBe}& 
				\textsf{LPYRamid}& 
				\textsf{SEXTrusion}& 
				\textsf{SLOOp} \\
				\hline
				\textsf{SVERtex}& 
				& 
				& 
				\\
				\hline
			\end{tabular}
			\label{tab4}
		\end{center}
	\end{table}
	
	\textbf{Negative 3D Geomset elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|}
				\hline
				\textsf{NGMSet NSBOx}& 
				\textsf{NSCOne}& 
				\textsf{NLSNout} \\
				\hline
				\textsf{NSDSh NSSLcylinder}& 
				\textsf{NSSPhere}& 
				\textsf{NLCYlinder} \\
				\hline
				\textsf{NSCYlinder NSCTorus}& 
				\textsf{NSREvolution}& 
				\textsf{NSRTorus} \\
				\hline
				\textsf{NLPYramid NSEXtrusion}& 
				\textsf{SLOOp}& 
				\textsf{SVERtex} \\
				\hline
			\end{tabular}
			\label{tab5}
		\end{center}
	\end{table}
	
	\textbf{Structural Geomset elements:}
	
	\textsf{GMSSet SRECtangle SANNulus SPROfile SPVErtex}
	
	\textbf{3D Pointset elements:}
	
	\textsf{PTSEt PTAXi PTCAr PTMIx}
	
	\textbf{Structural Pointset elements:}
	
	\textsf{PTSSet PLINe}
	
	\textbf{Dataset elements:}
	
	\textsf{DTSEt DATA}
	
	\textbf{Detailing Text elements:}
	
	\textsf{SDTExt DTEXt }\textsf{\textit{number}}
	
	\textbf{Material Text elements:}
	
	\textsf{SMTExt MTEXt }\textsf{\textit{number}}
	
	\textbf{Bolt Table elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|l|}
				\hline
				\textsf{BLTAble}& 
				\textsf{BLISt}& 
				\textsf{SBOLt}& 
				\textsf{LTABle} \\
				\hline
				\textsf{MBOLt}& 
				\textsf{MBLIst}& 
				\textsf{DTABle}& 
				\\
				\hline
			\end{tabular}
			\label{tab6}
		\end{center}
	\end{table}
	
	\textbf{Connection Table elements:}
	
	\textsf{CCTAble COCO}
	
	\textbf{Units elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|l|}
				\hline
				\textsf{UNIT}& 
				\textsf{MSET}& 
				\textsf{MTYPe}& 
				\textsf{ATLIst} \\
				\hline
				\textsf{USECtion}& 
				\textsf{UDEFinition}& 
				& 
				\\
				\hline
			\end{tabular}
			\label{tab7}
		\end{center}
	\end{table}
	
	\textbf{Group World elements:}
	
	\textsf{GPWL GROUp}
	
	\textbf{Specification World elements }(see the \textit{PDMS SPECON Reference Manual})\textbf{:}
	
	\textsf{SPWL SPECi SELEc SPCOm}
	
	\begin{itemize}
		\item \textbf{Specific Element Identifier }(\textless gid\textgreater )
	\end{itemize}
	
	This command part identifies a specific element either explicitly or by 
	reference to its relative position in the database hierarchy.
	
	\textbf{Examples}
	
	\textsf{/VALVE10 Named catalogue element SAME Previous element accessed}
	
	\textsf{OWN Owner of Current Element}
	
	\textsf{NEXT 2 2nd element in member list order at same level}
	
	\textsf{4 4th member of Current Element}
	
	\textsf{LAST 3 MEM 3rd last member of Current Element END Next element up in 
		hierarchy}
	
	\textsf{SECT Section above Current Element}
	
	\textsf{CATE 3 3rd Catego}ry
	
	\begin{itemize}
		\item \textbf{Cursor-picking Identifier }(\textless sgid\textgreater )
	\end{itemize}
	
	This command part defines the most general method of identifying an Element. 
	The command is completed by picking an element using the cursor in a 
	graphical view.
	
	\textbf{Examples}
	
	\textsf{ID @ Lowest level element hit by cursor ID SBOX @ Box primitive hit 
		by cursor}
	
	\textsf{ID SCOM @ Piping Component hit by cursor}
	
	\subsection{General PDMS Commands}
	\label{subsec:general}
	The commands in this chapter are available throughout PDMS.
	
	\subsection{Entering PARAGON}
	\label{subsubsec:entering}
	\textbf{Keyword: }\textbf{PARAGON}
	
	\textbf{Description: }This command is available throughout PDMS, allowing 
	PARAGON to be accessed at any time.
	
	\subsection{Leaving PARAGON}
	\label{subsubsec:leaving}
	At any point during a PARAGON session, you can elect to leave PARAGON and 
	enter another module of PDMS. This is simply a matter of inputting the name 
	of the module to be accessed. At this point, PARAGON will automatically save 
	the results of the working session and change to the new module. However, 
	all graphical displays, forms and menus will need to be redefined at the 
	beginning of the next session. In order to avoid having to redefine a view 
	and screen layout, it is possible to save the current status of a working 
	session by use of the \textbf{RECREATE }command.
	
	\subsection{Saving and Restoring the Current Display Status}
	\label{subsubsec:saving}
	\textbf{Keyword: }\textbf{RECREATE INSTALL}
	
	\textbf{Description: }If the intention is to leave PARAGON for a short 
	period only this facility allows the display definition and status 
	(including the full forms and menus set) to be saved, for restoration later.
	
	\textbf{NOTE: }Forms resized or moved using the cursor will be INSTALLed to 
	their original size.
	
	\textbf{Examples:}
	
	\textsf{RECREATE /PARA1 }- saves the display status in file /PARA1
	
	\textsf{RECREATE /PARA1 OVER }- as above, but an existing file /PARA1 is 
	overwritten
	
	\textsf{RECRE DISPLAY /PARA1 }- saves nodal settings, e.g. units, 
	representation etc.
	
	Read back in using {\$}M/\textit{name}
	
	\textsf{INSTALL SETUP /PARA1 }- restores the display definition stored in 
	file /PARA1
	
	\textbf{Command Syntax:}
	
	\textsf{\textgreater -- RECReate --}$+$\textsf{-- DISPlay }--.
	
	\textsf{\textbar \textbar }
	
	\textsf{`-------------}$+$\textsf{-- }\textsf{\textit{name 
	}}\textsf{--}$+$\textsf{-- OVERwrite --.}
	
	\textsf{\textbar \textbar }
	
	\textsf{`---------------}$+$\textsf{--\textgreater }
	
	\textsf{\textgreater -- INSTALL SETUP }\textsf{\textit{name 
	}}\textsf{--\textgreater }
	
	\subsection{Saving Work and Updating Databases}
	\label{subsubsec:mylabel2}
	\textbf{Keyword: }\textbf{SAVEWORK GETWORK}
	
	\textbf{Description: }These two commands are complementary. \textbf{SAVEWORK 
	}lets you update the databases to incorporate any changes you have made 
	during your current PARAGON session (since your last \textbf{SAVEWORK}). 
	\textbf{GETWORK }lets you refresh your view of all READ or Multiwrite 
	databases to pick up any changes that others may have made since you first 
	opened them.
	
	Both commands can be restricted to specific databases within the current MDB 
	by following them with a list of numbers. These numbers represent specific 
	databases in the order they appear in the output of the \textbf{STATUS 
	}command, which may be given in MONITOR or in the MDB mode of any GUI 
	module. If no database numbers are given, then the commands apply to the 
	whole MDB.
	
	It is good practice to use \textbf{SAVEWORK }frequently, to ensure maximum 
	data security. However, it should only be necessary to use \textbf{GETWORK 
	}when there are specific changes that you wish to pick up (in which case it 
	is likely that you will know which databases you will actually want to 
	refresh). \textbf{GETWORK }slows subsequent database access because the 
	information has to be re-read from disk, and should be avoided unless you 
	really need to use it.
	
	\textbf{GETWORK }automatically updates all volume views to reflect any 
	changes in shared databases.
	
	\subsection{Exit from PARAGON without Saving Changes}
	\label{subsubsec:mylabel3}
	\textbf{Keyword: }\textbf{QUIT FINISH}
	
	\textbf{Description: }This command exits from PARAGON without saving any 
	changes or the display setup. \textbf{QUIT }has the effect of deleting any 
	changes made since the last \textbf{SAVEWORK}, module change or MDB change.
	
	\textbf{Examples:}
	
	\textsf{QUIT }Exit from PARAGON (to MONITOR module)
	
	\textsf{QUIT DESIGN }Exit from PARAGON to DESIGN module
	
	\textsf{QUIT FINISH }Exit from PARAGON \textbf{and }from PDMS (returns to 
	operating system)
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{\textgreater -- QUIT --}$+$\textsf{-- }\textsf{\textit{modulename 
		}}--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- FINish \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`----------------}$+$\textsf{--\textgreater }
	
	\subsection{Saving the Alpha Readout to File}
	\label{subsubsec:mylabel4}
	\textbf{Keywords: }\textbf{ALPHA LOG ALPHA FILE}
	
	\textbf{Description: }This facility lets you save the alpha display 
	information to a text file in the computer operating system. Two types of 
	output are available, depending on the command used.
	
	\textbf{ALPHA LOG }enables the contents of either or both of the COMMANDS 
	and REQUESTS alpha regions to be written to a file.
	
	\textbf{ALPHA FILE }enables the contents of the REQUESTS region only to be 
	written to file.
	
	The ALPHA LOG/ ALPHA FILE facilities may be used to save data or as a 
	general output facility.
	
	\textbf{NOTE: }After an \textbf{ALPHA }file has been opened, subsequent 
	output will be directed to both the file and the screen until the file is 
	closed, or until you change to another PDMS module.
	
	\textbf{Examples:}
	
	\textsf{ALP LOG /LF1 COMMANDS }- log information displayed in the COMMANDS
	
	region in file /LF1
	
	\textsf{ALP LOG /LF1 OVER COMM }- as above, but overwrite existing file /LF1
	
	\textsf{ALP LOG /LF2 }- log information displayed in both alpha regions
	
	in file /LF2
	
	\textsf{ALP FILE /LF2 }-log information displayed in REQUESTS region
	
	only
	
	\textsf{ALP LOG END }- finish logging information
	
	\textsf{ALP FILE END}
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{\textgreater -- ALPha --}$+$\textsf{-- LOG --}$+$\textsf{-- 
		}\textsf{\textit{name }}\textsf{--}$+$\textsf{-- OVERwrite }--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar -- APPend \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar \textbar `---------------}$+$\textsf{-- COMMands --.}
	
	\textsf{\textbar `-- END --\textgreater \textbar \textbar }
	
	\textsf{\textbar \textbar -- REQuests --\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar `--------------}$+$\textsf{--\textgreater }
	
	\textsf{\textbar }
	
	\textsf{`-- FILE --}$+$\textsf{-- }\textsf{\textit{name 
	}}\textsf{--}$+$\textsf{-- OVERwrite --.}
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- APPend \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar `---------------}$+$\textsf{--\textgreater `-- END 
		--\textgreater }
	
	\subsection{Audible Error Trace}
	\label{subsubsec:audible}
	\textbf{Keywords: }\textbf{ALARM}
	
	\textbf{Description: }When a macro error occurs, there is an audible alarm 
	at the workstation to signal that the error has occurred. Occasionally, 
	macro errors can be anticipated and no audible warning is required. This 
	command allows the audible warning to be switched on or off either 
	interactively or via a macro.
	
	If the audible warning is ON, it will sound whenever an error alert is 
	displayed.
	
	\textbf{Examples:}
	
	\textsf{ALARM ON }Switches the audible tone on (this is the default).
	
	\textsf{ALARM OFF }Suppresses the audible tone until it is turned on again.
	
	\textbf{Command Syntax:}
	
	\textsf{\textgreater -- ALARM --}$+$\textsf{-- ON }---.
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- OFF --}$+$\textsf{--\textgreater }
	
	\subsection{Switching Text Output Off}
	\label{subsubsec:switching}
	\textbf{Keywords: }\textbf{TRACE}
	
	\textbf{Description: }This command, applicable in TTY mode only, controls 
	the automatic output of the Current Element name and attributes. With Trace 
	set to
	
	\textbf{Examples:}
	
	ON, the attributes display is automatically updated for each element 
	accessed. With Trace set to OFF, the attribute display is not changed. When 
	macros are being run, TRACE is always set to OFF automatically.
	
	\textsf{TRACE OFF }Stops the automatic output of attribute data.
	
	\textsf{TRACE ON }Restarts automatic output of Current Element name and 
	attributes.
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{\textgreater -- TRAce --}$+$\textsf{-- ON }---.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`-- OFF --}$+$\textsf{--\textgreater }
	
	\subsection{Defining Colours}
	\label{subsubsec:defining}
	\textbf{Keywords: }\textbf{COLOUR ACTIVE CE VISIBLE AIDS}
	
	\textbf{Description: }These commands allow colours to be defined so that the 
	status of different types of item in the display may be distinguished by 
	means of colour. The colours used have default settings, but these may be 
	redefined.
	
	The colours may be assigned by using the \textbf{COLOUR }command to define 
	the Red-Green-Blue mix for a colour number or to assign a predefined colour 
	mix by name. PARAGON allows the use of 100 user-definable colours, plus some 
	specific ones which are assigned to items which need to be readily 
	distinguishable in the display.
	
	\textbf{Definitions:}
	
	\begin{itemize}
		\item The \textbf{Active }colour is used for the catalogue component being worked on (the \textbf{significant element}, e.g. ELBO, VALV). If the current element is a geometric primitive, the active colour is used for all primitives owned by the significant element \textit{except }the current primitive.
		\item The \textbf{CE }colour is used for the element currently being accessed (i.e. the element highlighted in the Members list). This may be either a primitive or a significant element.
		\item The \textbf{Visible }colour is used for any element in the display other than those to which the active or CE colours apply.
		\item The Active and Visible elements together constitute the \textbf{Draw List}.
	\end{itemize}
	
	The \textbf{predefined colour mixes }which you may specify by name are as 
	follows:
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{89pt}|p{59pt}|p{60pt}|p{38pt}|}
				\hline
				\textbf{Colour} \par black& 
				\textbf{Red} \par & 
				\textbf{Green} \par & 
				\textbf{Blue} \par \\
				\hline
				white& 
				100& 
				100& 
				100 \\
				\hline
				whitesmoke& 
				96& 
				96& 
				96 \\
				\hline
				ivory& 
				93& 
				93& 
				88 \\
				\hline
				grey& 
				66& 
				66& 
				66 \\
				\hline
				lightgrey& 
				75& 
				75& 
				75 \\
				\hline
				darkgrey& 
				32& 
				55& 
				55 \\
				\hline
				darkslate& 
				18& 
				31& 
				31 \\
				\hline
				red& 
				80& 
				& 
				\\
				\hline
				brightred& 
				100& 
				& 
				\\
				\hline
				coralred& 
				80& 
				36& 
				27 \\
				\hline
				tomato& 
				100& 
				39& 
				28 \\
				\hline
				plum& 
				55& 
				40& 
				55 \\
				\hline
				deeppink& 
				93& 
				7& 
				54 \\
				\hline
				pink& 
				80& 
				57& 
				62 \\
				\hline
				salmon& 
				98& 
				50& 
				44 \\
				\hline
				orange& 
				93& 
				60& 
				\\
				\hline
				brightorange& 
				100& 
				65& 
				\\
				\hline
				orangered& 
				100& 
				50& 
				\\
				\hline
				maroon& 
				56& 
				14& 
				42 \\
				\hline
				yellow& 
				80& 
				80& 
				\\
				\hline
				gold& 
				93& 
				79& 
				20 \\
				\hline
				lightyellow& 
				93& 
				93& 
				82 \\
				\hline
				lightgold& 
				93& 
				91& 
				67 \\
				\hline
				yellowgreen& 
				60& 
				80& 
				20 \\
				\hline
				springgreen& 
				& 
				100& 
				50 \\
				\hline
				green& 
				& 
				80& 
				\\
				\hline
				forestgreen& 
				14& 
				56& 
				14 \\
				\hline
				darkgreen& 
				18& 
				31& 
				18 \\
				\hline
				cyan& 
				& 
				93& 
				93 \\
				\hline
				turquoise& 
				& 
				75& 
				80 \\
				\hline
				aquamarine& 
				46& 
				93& 
				78 \\
				\hline
				blue& 
				& 
				& 
				80 \\
				\hline
				royalblue& 
				28& 
				46& 
				100 \\
				\hline
				navyblue& 
				& 
				& 
				50 \\
				\hline
				powderblue& 
				69& 
				88& 
				90 \\
				\hline
				midnight& 
				18& 
				18& 
				31 \\
				\hline
				steelblue& 
				28& 
				51& 
				71 \\
				\hline
				indigo& 
				20& 
				& 
				40 \\
				\hline
				mauve& 
				40& 
				& 
				60 \\
				\hline
				violet& 
				93& 
				51& 
				93 \\
				\hline
				magenta& 
				87& 
				& 
				87 \\
				\hline
			\end{tabular}
			\label{tab8}
		\end{center}
	\end{table}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{87pt}|l|l|l|}
				\hline
				\textbf{Colour}& 
				\textbf{Red}& 
				\textbf{Green}& 
				\textbf{Blue} \\
				\hline
				beige& 
				96& 
				96& 
				86 \\
				\hline
				wheat& 
				96& 
				87& 
				70 \\
				\hline
				tan& 
				86& 
				58& 
				44 \\
				\hline
				sandybrown& 
				96& 
				65& 
				37 \\
				\hline
				brown& 
				80& 
				17& 
				17 \\
				\hline
				khaki& 
				62& 
				62& 
				37 \\
				\hline
				chocolate& 
				93& 
				46& 
				13 \\
				\hline
				darkbrown& 
				55& 
				27& 
				8 \\
				\hline
			\end{tabular}
			\label{tab9}
		\end{center}
	\end{table}
	
	The \textbf{default colour assignments }are:
	
	\textbf{Colour No Colour}
	
	Current element yellow
	
	Visible elements lightgrey
	
	\begin{enumerate}
		\item grey
		\item red
		\item orange
		\item yellow
		\item green
		\item cyan
		\item blue
		\item violet
		\item brown
		\item white
		\item pink
		\item mauve
		\item turquoise
		\item indigo
		\item black
		\item magenta
	\end{enumerate}
	
	\textbf{Examples:}
	
	\textsf{COL 5 DARKGREEN }Colour 5 will be changed to dark green
	
	\begin{center}
		\textsf{COL 3 MIX RED 50 GRE 50 BLU 5 }Colour 3 will change to the specified
	\end{center}
	
	mix of red, green and blue
	
	\textsf{COL VISIBLE BRIGHTRED }Sets the colour for displaying components to 
	bright red
	
	\textbf{NOTE: }When colours are mixed in their Red, Green and Blue 
	constituents, the command line must contain values for all three 
	constituents in the correct order. The numbers entered for the relative 
	proportions of the basic colours must each be in the range 0-100, but they 
	are not percentages of the overall colour and so do not need to add up to 
	100.
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{\textgreater -- COLour -}$+$\textsf{- }\textsf{\textit{integer }}-.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar - ACTIVE --\textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar - CE \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`- VISIble -}$+$\textsf{- }\textsf{\textit{colour\textunderscore 
			name }}\textsf{--\textgreater }
	
	\textsf{\textbar }
	
	\textsf{`- MIX RED }\textsf{\textit{integer }}\textsf{GREen 
	}\textsf{\textit{integer }}\textsf{BLUe }\textsf{\textit{integer 
			--\textgreater }}
	
	where \textsf{\textit{colour\textunderscore name }}is the name of any of the 
	predefined colour mixes listed above.
	
	\textbf{Querying:}
	
	\begin{flushright}
		\textsf{\textgreater -- Q COLour --}$+$\textsf{-- }\textsf{\textit{integer 
		}}--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar -- ACTIVE \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- CE \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- VISIble -----}$+$\textsf{--\textgreater }
	
	\section{The Catalogue Database}
	\label{sec:mylabel1}
	This chapter details the structure of the PDMS Catalogue database.
	
	Note that words of four or five uppercase characters which appear in this 
	chapter (for example, CATA, BLTA, SPREF) are PDMS element names. When an 
	element's member list is queried in PDMS, each element type will be 
	displayed as a four-character name. Five or six characters are occasionally 
	used in this chapter where this gives a `PDMS' name which is closer to the 
	element's `English' name, for example SPREF (instead of SPRE) for 
	Specification Reference.
	
	\subsection{What is the Catalogue For?}
	\label{subsubsec:mylabel5}
	The Catalogue in PDMS serves a purpose similar to a parts catalogue to which 
	a pipework designer or structure designer would refer when using 
	`conventional' design methods. It contains details of all available 
	components (piping and structural), including their dimensions, geometry and 
	drawing symbols. Whereas the conventional parts catalogue is a book held in 
	the Design Office, the PDMS Catalogue is a database held on the computer.
	
	\subsection{Principal Features of the Catalogue Database}
	\label{subsubsec:principal}
	If a new Catalogue database (DB) is required, PARAGON can be used to 
	construct it - see Chapter 8 for details of creating and manipulating a 
	Catalogue DB using PARAGON.
	
	The Catalogue data is held according to a strict hierarchy which is similar 
	in form to that of the Design data.
	
	When a Component is selected by the designer using DESIGN, a Specification 
	Reference (SPREF) is identified and held in the Design database. The SPREF 
	points to a Specification Component (SPCOM) in the Specification. This in 
	turn points to a Catalogue Component (SCOM, SPRF, SJOI, SFIT, etc.) in the 
	Catalogue (see Figure 4- 1).
	
	Whereas the Design data is specific to a particular design, Catalogues and 
	Specifications may be specific to a company but general to a number of 
	projects in that company. For example, the same Catalogue Component may be 
	referred to many times in a particular design and may also appear in other 
	design projects proceeding at the same time.
	
	Catalogues are usually built up as a library of catalogue macros. A 
	selection of these macros can then be used to build up a project-specific 
	Catalogue database containing only those Components which might be used on 
	that project.
	
	Design Specification Catalogue
	
	\textbf{Figure 4-1 }Interrelationship between Design Data, Catalogue and 
	Specifications
	
	\subsection{Structure of the Catalogue Database}
	\label{subsubsec:structure}
	Catalogues are constructed as a hierarchy of \textbf{elements}. Each element 
	has certain \textbf{attributes }and some may contain further member 
	elements. The complete Catalogue hierarchy is shown in Figure 4-2.
	
	Note that in any discussion of \textbf{attributes }which may appear in the 
	rest of this chapter, the `standard' attributes of TYPE, NAME, OWNER and 
	LOCK will not be mentioned, as these are common to \textit{all }the elements described 
	below.
	
	In addition, \textit{user-defined attributes }(UDAs) may be used with Catalogue database elements - see the 
	\textit{LEXICON Reference Manual }for details.
	
	\begin{center}
		WORLD
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.04in,height=1.78in]{Paragon5}}
		\label{fig5}
	\end{figure}
	
	(Connections) (Bolts) (Units) (Specifications) (Groups)
	
	CCTA
	
	BLTA
	
	CATA
	
	UNIT
	
	SPWL
	
	GPWL
	
	COCO
	
	BLIS SBOL
	
	LTAB DTAB
	
	MBLI MBOL
	
	MSET USEC
	
	MTYP UDEF ATLI
	
	SPEC
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.01in,height=0.12in]{Paragon6}}
		\label{fig6}
	\end{figure}
	
	SELEC SPCO
	
	GROU
	
	(Piping Catalogue) (Steelwork Catalogue)
	
	SECT STSE
	
	CATE STCA
	
	\begin{flushright}
		GMSE
	\end{flushright}
	
	GMSE
	
	MTEX
	
	SPRF
	
	SFIT GMSS PTSS
	
	GMSE
	
	NGMS
	
	PTSE
	
	SMTE
	
	SCOM
	
	SBOX
	
	PTSE
	
	DTEX BLTP
	
	DTSE
	
	SJOI
	
	SREC
	
	PLIN
	
	SBOX
	
	NSBO
	
	SDTE PTCA
	
	DTSE
	
	BOXI LSNO SCON
	
	PTCA PTAX PTMI
	
	\begin{flushright}
		DATA \underline { }$^{SANN\, }$SPRO
	\end{flushright}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.01in,height=0.12in]{Paragon7}}
		\label{fig7}
	\end{figure}
	
	\begin{flushright}
		SPVE
	\end{flushright}
	
	BOXI
	
	LSNO NLSN SCON NSCO
	
	PTAX PTMI
	
	\textbf{DATA}
	
	SSPH
	
	LCYL SCYL SSLC SCTO SRTO TUBE LPYR SDIS SDSH LINE SEXT
	
	SSPH
	
	LCYL SCYL SSLC SCTO SRTO TUBE LPYR SDIS SDSH LINE SEXT
	
	NSSP
	
	NLCY NSCY NSSL NSCT NSRT
	
	NLPY
	
	NSDS NSEX
	
	SREV SREV NSRE
	
	\begin{flushright}
		SLOO
	\end{flushright}
	
	\begin{flushright}
		SLOO
	\end{flushright}
	
	SLOO
	
	\begin{flushright}
		SVER
	\end{flushright}
	
	\begin{flushright}
		SVER
	\end{flushright}
	
	SVER
	
	NOTES:
	
	For ease of interpretation in text:
	
	SCOM $=$ COMP SPRF $=$ PROF SJOI $=$ JOIN SFIT $=$ FITT SDTE $=$ DTEX
	
	CATE/STCA (Category) elements are optional. Their members can be owned 
	directly by a SECT/STSE.
	
	SMTE $=$ MTEX TEXT elements, which can
	
	appear at several positions in the
	
	Any negative 3D primitive (as shown below NGMS) can also be owned by any 
	positive 3D primitive.
	
	hierarchy, have been omitted for clarity.
	
	\begin{center}
		\textbf{Figure 4-2 }The Catalogue Database Hierarchy
	\end{center}
	
	\subsection{Catalogue (CATA)}
	\label{subsubsec:catalogue}
	CATA is the highest level element of the Catalogue hierarchy. Its attributes 
	include:
	
	\begin{itemize}
		\item \textbf{DESC }- a text description of the catalogue.
		\item \textbf{PURP }- a PDMS word showing the specific purpose for which that catalogue is intended. This should be set to the same word as the Specification with which it is to be used; e.g. PIPE, FITT.
		\item \textbf{CSTA }- the Catalogue standard.
	\end{itemize}
	
	A CATA can contain a number of \textbf{Catalogue Sections}. These are of two 
	types: \textbf{Piping Sections }(SECT) and \textbf{Structural Sections 
	}(STSEC). They are the principal administrative elements by which the 
	Catalogue is divided and arranged. The Catalogue can also contain 
	\textbf{Text }elements (TEXT) - see Section 9.6.
	
	All elements referred to in a \textbf{Specification }(see the \textit{SPECON Reference Guide}) \textit{must }exist within 
	a CATA hierarchy, although elements may exist within a CATA which are not 
	referred to by a Specification.
	
	Note that the following elements may also exist within the Catalogue 
	database at the same level as CATA:
	
	\begin{itemize}
		\item Units World (UNITS)
		\item Connection Tables (CCTAB)
		\item Bolt Tables (BLTAB)
		\item Specification World (SPWL)
		\item Group World (GPWL)
	\end{itemize}
	
	Units, Connection Tables and Bolt Tables are described in Chapter 9 of this 
	manual, the latter element type being described in more detail in the 
	\textit{ISODRAFT Reference Manual}. Specification World elements are detailed in the \textit{SPECON Reference Manual}.
	
	\subsection{Catalogue Sections (SECT and STSEC) and Categories (CATE and STCA)}
	\label{subsubsec:mylabel6}
	Sections and Categories are administrative elements which let you segregate 
	particular types of catalogue data into logical parts of the hierarchy. 
	Sections, which subdivide an overall CATA, are obligatory; Categories, which 
	subdivide Sections, are optional (although their use is recommended).
	
	There are two types of Catalogue Section: \textbf{Piping Sections }(SECT) 
	and \textbf{Structural Sections }(STSEC). Both have the following 
	attributes:
	
	\begin{itemize}
		\item \textbf{DESC }- a textual description of the section.
		\item \textbf{PURP }- a PDMS word showing the specific purpose for which that section is intended.
		\item \textbf{GTYP }- a PDMS word showing the generic type for elements contained in the section. This should be the same word as that used to identify the elements in DESIGN; e.g. VALV, BEAM.
	\end{itemize}
	
	Similarly, there are two types of Category: \textbf{Piping Category }(CATE) 
	and \textbf{Structural Category }(STCA). Both have the following principal 
	attributes:
	
	\begin{itemize}
		\item \textbf{DESC } a textual description of the category.
		\item \textbf{PURP }- a PDMS word showing the specific purpose for which that category is intended. This should be set to the same STYPE as in the Specification with which it is to be used; e.g. GLOB, GATE etc. for a VALV.
		\item \textbf{GTYP }- a PDMS word showing the generic type for elements contained in the section.
		\item \textbf{SKEY }- a textual symbol key showing how the item is represented in isometric drawings (see the \textit{ISODRAFT Reference Manual}).
		\item \textbf{PTRE }- a reference to a 3D P-point Set (PTSE).
		\item \textbf{GMRE }- a reference to a 3D Geometry Set (GMSE).
		\item \textbf{DTRE }- a reference to a Data Set (DTSE).
		\item \textbf{CDET }- a reference to Detailing Text (DTEX).
	\end{itemize}
	
	Both types of Catalogue Section or Category contain the elements \textbf{3D 
		P-point Set, 3D Geometry Set, Data Set}, \textbf{Detailing Text }and 
	\textbf{Material Text}, as described in Section
	
	\begin{enumerate}
		\item Piping Sections/Categories may also contain \textbf{Piping Components}, as described in Section 4.5.2. Structural Sections/Categories may also contain \textbf{Structural Components }(\textbf{Profiles, Joints }and \textbf{Fittings}), \textbf{Structural Pointsets, Negative 3D Geometry Sets }and \textbf{Structural Geometry Sets}, as described in Section 4.5.3.
	\end{enumerate}
	
	\subsubsection{Elements Used in Both Types of Catalogue Section/Category}
	\label{para:elements}
	The following elements may be used in either type of Catalogue Section or 
	Category:
	
	\begin{itemize}
		\item \textbf{3D P-point Set }(PTSET) (usually abbreviated to \textbf{3D Pointset}) - a definition of the position, direction, connection type and bore of a Component's P-points, to be used by DESIGN, ISODRAFT, etc.
		\item \textbf{3D Geometry Set }(GMSET) (usually abbreviated to \textbf{3D Geomset}) - a grouping of 3D primitive elements, defining the dimensions, orientation and obstruction geometry of each primitive. Used by DESIGN and the Drawing modules.
		\item \textbf{Data Set }(DTSET) (usually abbreviated to \textbf{Dataset}) - a grouping of DATA elements, holding any catalogue data not stored more specifically elsewhere and which is required for use in DESIGN or DRAFT; e.g. the cross-sectional area of a structural steel member calculated from its parameterised dimensions.
		\item \textbf{Detailing Text }(DTEX) - elements containing general descriptive text relating to a Component. Referred to from SPCOM elements in the Specification. For further details see Section 9.1.
		\item \textbf{Material Text }(MTEX) - elements containing text describing the material(s) from which the physical Component is constructed. Referred to from SPCOM elements in the Specification. For further details see Section 9.2.
	\end{itemize}
	
	\subsubsection{Elements Used in Piping Sections/Categories}
	\label{para:mylabel2}
	A Piping Section or Category may contain all those elements listed in 
	Section 4.5.1 plus the following:
	
	\begin{itemize}
		\item \textbf{Piping Component }(COMP) - an element defining a piece of pipework. It consists of a list of values (known as \textbf{component parameters}) and references to a \textbf{3D Pointset }element and a \textbf{3D Geomset }element. The Pointset and Geomset make use of the component parameter values in defining the size, geometry and connection types of the Piping Component.
	\end{itemize}
	
	\subsubsection{Elements Used in Structural Sections/Categories}
	\label{para:mylabel3}
	A Structural Section or Category may contain all those elements listed in 
	Section 4.5.1 plus the following:
	
	\begin{itemize}
		\item \textbf{Structural Pointset }(PTSSET) - a definition of the position and direction of a Component's P-lines, to be used by DESIGN.
		\item \textbf{Negative 3D Geometry Set }(NGMSET) (usually abbreviated to \textbf{Negative 3D Geomset}) a grouping of 3D negative primitive elements (representing holes, end
	\end{itemize}
	
	preparations etc.), defining the dimensions, orientation and obstruction 
	geometry of each primitive. Used by DESIGN and the Drawing modules.
	
	\begin{itemize}
		\item \textbf{Structural Geometry Set }(GMSSET) (usually abbreviated to \textbf{Structural Geomset}) - a grouping of 2D primitive elements, defining the dimensions, orientation and obstruction geometry of each primitive. Used by DESIGN and the Drawing modules.
		\item \textbf{Profile }(PROF) - a 2D structural Component defining the cross-section of a beam, column etc. (a Section). It consists of a list of component parameters and references to a \textbf{Structural Pointset }element and a \textbf{Structural Geomset }element. The Pointset and Geomset make use of the component parameter values in defining the size and geometry of the Component. In the design process, a length is associated with a Profile to produce a Section.
		\item \textbf{Joint }(JOIN) - a 3D structural Component defining a physical means of attaching one Section to another. It consists of a list of component parameters and references to a \textbf{Structural Pointset }element, a \textbf{3D Pointset }element and a \textbf{3D Geomset }element. The two Pointsets and the Geomset make use of the component parameter values in defining the size and geometry of the Component.
		\item \textbf{Fitting }(FITT) - a 3D structural Component defining an object which is physically attached to a Section but is not part of the structure formed by Sections and Joints. For example, a Fitting may be used to attach a pipe hanger to a Section. The element consists of a list of component parameters and references to a \textbf{3D Pointset }element and a \textbf{3D Geomset }element. The Pointset and Geomset make use of the component parameter values in defining the size and geometry of the Component.
	\end{itemize}
	
	The Catalogue structure as described so far may be used in various ways, but 
	the recommended method of use is to place only one type of element in each 
	Catalogue Section, and to place different kinds of Components in different 
	Catalogue Categories. For example, you might place all 3D Pointsets for 
	Piping Components in one Piping Section and all 3D Geomsets for Piping 
	Components in another, with separate Piping Sections for equal tees and 
	reducing tees. When defining Profiles, you might place Profiles for 
	Universal Beams in one Structural Section, Profiles for Unequal Angles in 
	another, and so on.
	
	\subsection{Text (TEXT)}
	\label{subsubsec:mylabel7}
	The Text is a general element that can occupy many positions in the 
	hierarchy. It can be used to store additional information about an owning or 
	adjacent element. The TEXT element should not be confused with the MTEX and 
	DTEX elements described in Section 4.5.1. See Section 9.6 for further 
	details.
	
	\subsection{Parameters}
	\label{subsubsec:parameters}
	Parameters define the size, geometry and other characteristics of 
	Components. They are used in setting the attributes of the Pointsets, 
	Geomsets and Datasets to which Component elements refer.
	
	All classes of Component can use \textbf{component parameters}, 
	\textbf{design parameters }and \textbf{insulation parameters}. Structural 
	Components can also use \textbf{attached }and \textbf{owning design 
		parameters}. Component parameters are defined in the Catalogue; the other 
	classes of parameters allow characteristics to be set during the design 
	process.
	
	\subsubsection{Component Parameters}
	\label{para:component}
	Piping Components (COMP), Profiles (PROF), Joints (JOIN) and Fittings (FITT) 
	all have a PARAM attribute which lists the component parameters.
	
	Section 8.2 describes how to set up the component parameters of a Component. 
	You may define default values which PARAGON will use if you are working with 
	a Component whose component parameters have not been set up. The values are 
	set using the \textbf{MODEL SETTINGS }command. For example,
	
	\textsf{MODEL SETTINGS PARAM 1 10}
	
	defines a default value of 10 for component parameter number 1. See Section 
	6.4.1 for the full syntax of how to set default values.
	
	These default values are set up only for the current PARAGON session. They 
	are not stored in the Catalogue DB. You must define the component parameters 
	of a Component before you use it in the Design DB.
	
	\subsubsection{Insulation Parameters}
	\label{para:insulation}
	A design element in the Design DB refers to a main Catalogue Component 
	(indirectly) via its Specification Reference (SPREF) attribute. The design 
	element may also refer to a second Catalogue Component which defines the 
	insulation of the first Component, via its Insulation Specification (ISPEC) 
	attribute. The second Component is the \textbf{Insulation Component }of the 
	design element.
	
	Insulation parameters (IPARAM) allow the main Component to take dimensions 
	from the Insulation Component. When the main Component uses IPARAM 3, for 
	example, it picks up the value of the PARAM 3 of the corresponding 
	Insulation Component.
	
	When you define a Catalogue Component using insulation parameters, its 
	dimensions are not completely specified in the Catalogue. So that PARAGON 
	can give some idea of what the Component will look like when used in a 
	design, you can define specimen values for the insulation parameters. These 
	specimen values apply to all Components, unlike the component parameters 
	which are attributes of a particular Component. The values are set using the 
	\textbf{MODEL SETTINGS }command. For example,
	
	\textsf{MODEL SETTINGS IPARAM 3 25}
	
	defines a specimen value for insulation parameter number 3. See Section 
	6.4.5 for the full syntax of how to set values for insulation parameters. 
	The values are not stored in the Catalogue DB; they are set up only for the 
	current PARAGON session.
	
	\subsubsection{Structural Parameters}
	\label{para:structural}
	These allow Joint and Fitting Components to take dimensions from the Section 
	or Sections (beam, column, etc.) to which they are physically connected. In 
	this way, a basic design of Joint or Fitting may be adjusted automatically 
	in the Design DB to fit a connected Section of any size. (Structural 
	parameters are meaningless for Profiles.)
	
	Structural parameters are of four types:
	
	\begin{itemize}
		\item \textbf{Attached parameters }(APARAM)
		\item \textbf{Owning parameters }(OPARAM)
		\item \textbf{Design attached parameters }(DES APARAM)
		\item \textbf{Design owning parameters }(DES OPARAM).
	\end{itemize}
	
	The types of structural parameter that a Component can use depends on 
	whether it is a Piping Component, Profile, Joint or Fitting. In the case of 
	a Joint, it also depends on how the Component is used in the Design DB.
	
	Joints are of two types: primary and secondary. A primary Joint has an 
	\textbf{attached }Section in the Design DB; a secondary Joint has an 
	\textbf{attached }Section and an \textbf{owning }Section. (See the \textit{DESIGN Reference Manual }for 
	details of primary and secondary Joints.) Note that primary and secondary 
	Joints are represented by the same class of Catalogue Component, but the 
	settings of their attributes and the attributes of their Pointsets and 
	Geomsets are different.
	
	A Fitting Component has an \textbf{owning }Section in the Design DB.
	
	Components which have an attached Section (i.e. primary and secondary 
	Joints) can use attached parameters to define the attributes of their 
	Pointsets and Geomsets. Attached parameters correspond to the component 
	parameters of the attached Section. For example, when a Joint component uses 
	APARAM 2, it picks up the value of the PARAM 2 of the Joint's attached 
	Section.
	
	Similarly, Components which have an owning Section (i.e. secondary Joints 
	and Fittings) can use owning parameters in defining the attributes of their 
	Pointsets and Geomsets. Owning parameters correspond to the component 
	parameters of the owning Section. For example, when a Joint or Fitting 
	component uses OPARAM 5, it picks up the value of the PARAM 5 of the 
	component's owning Section.
	
	You can define specimen values for structural parameters in the same way as 
	for insulation parameters. For example,
	
	\textsf{MODEL SETTINGS APARAM 2 300}
	
	defines a specimen value of 300 for attached parameter number 2. See Section 
	5.9 for the full syntax of how to set values for structural parameters.
	
	\subsubsection{Design DB Parameters}
	\label{para:design}
	These allow structural Components to take dimensions from Design Parameter 
	Arrays in the Design DB. Each design element has a Design Parameter Array 
	with ten values. (See the \textit{DESIGN Reference Manual }for further details.)
	
	Design DB parameters are of three types:
	
	\begin{itemize}
		\item \textbf{Design parameters }(DES PARAM)
		\item \textbf{Design attached parameters }(DES APARAM, structural items only)
		\item \textbf{Design owning parameters }(DES OPARAM, structural items only)
	\end{itemize}
	
	\textbf{Design parameters }allow any component with an SPREF to use values 
	from the design element which refers to it (via the SPREF). For example, the 
	DES PARAM 4 of a Component is the fourth value in the Design Parameter Array 
	of the design element.
	
	Design parameters can be used anywhere that component parameters can be 
	used.
	
	\textbf{Design attached parameters }and \textbf{design owning parameters 
	}allow a Joint or Fitting Component to use values from the design elements 
	which represent its attached and owning Sections. (Attached and owning 
	sections are explained in Section 4.7.3.) For example, the DES OPARAM 1 of a 
	Component is the first value in the Design Parameter Array of the design 
	element of its owning Section. Design attached parameters can be used 
	anywhere that attached parameters can be used. Similarly, design owning 
	parameters in place of owning parameters.
	
	You can define specimen values for Design DB parameters in the same way as 
	for insulation parameters. For example,
	
	\textsf{MODEL SETTINGS DES PARAM 7 9.5}
	
	defines a specimen value of 9.5 for design parameter number 7. See Section 
	6.4.1 for the full syntax of how to set values for Design DB parameters.
	
	Figure 4-3 summarises how the various types of parameters may be used with 
	the different classes of Component.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.01in,height=0.12in]{Paragon8}}
		\label{fig8}
	\end{figure}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{146pt}|p{95pt}|p{45pt}|p{43pt}|p{38pt}|p{38pt}|p{42pt}|}
				\hline
				\textbf{Parameter:}& 
				\textbf{Applicable to:} \par & 
				\textbf{Piping} \par \textsf{\textbf{Comp't}} \par \textbf{(COMP)}& 
				\textbf{Profile} \par \textbf{(PROF)}& 
				\textbf{Prim'y Joint} \par \textbf{(PJOI)}& 
				\textbf{Sec'y Joint} \par \textbf{(SJOI)}& 
				\textbf{Fitting} \par \textbf{(FITT)} \\
				\hline
				\textbf{Catalogue Component Parameters}& 
				\textbf{(PARAM)}& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $ \\
				\hline
				\textbf{Insulation Parameters}& 
				\textbf{(IPARAM)}& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $ \\
				\hline
				\textbf{Attached Parameters (Structural)}& 
				\textbf{(APARAM)}& 
				& 
				& 
				$\beta $& 
				$\beta $& 
				\\
				\hline
				\textbf{Owning Parameters (Structural)}& 
				\textbf{(OPARAM)}& 
				& 
				& 
				& 
				$\beta $& 
				$\beta $ \\
				\hline
				\textbf{Design Parameters (Design DB)}& 
				\textbf{(DES PARAM)}& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $& 
				$\beta $ \\
				\hline
				\textbf{Design Attached Parameters}& 
				\textbf{(DES APARAM)}& 
				& 
				& 
				$\beta $& 
				$\beta $& 
				\\
				\hline
				\textbf{Design Owning Parameters}& 
				\textbf{(DES OPARAM)}& 
				& 
				& 
				& 
				$\beta $& 
				$\beta $ \\
				\hline
			\end{tabular}
			\label{tab10}
		\end{center}
	\end{table}
	
	\begin{center}
		\textbf{Figure 4-3 }Table of Parameters and Components
	\end{center}
	
	\subsection{Catalogue Components}
	\label{subsubsec:mylabel8}
	There are four classes of Catalogue Component:
	
	\begin{itemize}
		\item Piping Component
		\item Profile
		\item Joint
		\item Fitting.
	\end{itemize}
	
	Their attributes are described in the following sections. These attributes 
	(other than the component parameters) must be set to actual values (words or 
	references to other elements). They cannot be defined using parameters.
	
	A reference to an element is usually set to the name of the element, for 
	example \textsf{/PTSR3}, but it can also be set as a \textbf{general 
		identifier}, for example:
	
	\textsf{PTSE 4 OF SECT 2 OF CATA /ASA-CATA}
	
	The attributes of \textbf{Pointsets }and \textbf{Geomsets }may be defined 
	using component parameters, design parameters and insulation parameters. 
	Where appropriate, attributes for structural items may also be defined using 
	design owning parameters and design attached parameters.
	
	A component parameter may be a numeric value, an expression or a word. (The 
	full syntax for expressions is defined in the \textit{Plant Design Software Customisation Guide}.) An insulation parameter, a 
	structural parameter or a Design DB parameter may only be a numeric value or 
	an expression. The values assigned to parameters and the use to which they 
	are put, and the number of parameters used, are arbitrary, depending only on 
	the skill and experience of the user. Chapter 8 contains examples of the 
	parameterisation of typical Components.
	
	Catalogue Components do not have member elements.
	
	\subsubsection{Piping Component (COMP; SCOM)}
	\label{para:piping}
	The attributes of a Piping Component are:
	
	\begin{itemize}
		\item \textbf{PTREF }- reference to a 3D Pointset element.
		\item \textbf{GMREF }- reference to a 3D Geomset element.
		\item \textbf{PARAM }- the component parameters, a list of values used in the 3D Pointset and 3D Geomset to define the Component.
		\item \textbf{GTYPE }- a word attribute indicating the generic type of the Piping Component, selected from the following:
	\end{itemize}
	ATTA - attachment
	
	BEND - pipe bend
	
	CAP - end cap
	
	CLOS - closure
	
	COUP - coupling
	
	CROS - cross piece
	
	DUCT - ducting
	
	ELBO - fitting elbow
	
	FBLI - blind flange
	
	FILT - filter FLAN or FLG flange
	
	FTUB - fixed length tube
	
	GASK - gasket
	
	HELE - hanger element
	
	INST - instrument
	
	INSU - insulation
	
	LJSE - lap joint stub end
	
	NOZZ - nozzle
	
	OLET - weldolets
	
	PCOM - pipe component
	
	REDU - reducer
	
	SHU - standard hook-up
	
	TEE - fitting tee
	
	TRAC - tracing
	
	TRAP - steam trap
	
	TUBE - implied tube
	
	UNIO - union
	
	VALV - valve
	
	VENT - open-ended pipe or vent
	
	VFWA - four-way valve
	
	VTWA - three-way valve
	
	WELD - weld
	
	The GTYPE \textit{must }be set as one of the above, otherwise a data consistency check on 
	a Branch containing the Component (see the \textit{DESIGN Reference Manual}) will not work correctly.
	
	\begin{itemize}
		\item \textbf{DTREF }- reference to a Dataset element.
	\end{itemize}
	
	\subsubsection{Profile (PROF; SPRF)}
	\label{para:profile}
	The attributes of a Profile are:
	
	\begin{itemize}
		\item \textbf{PSTREF }- reference to a Structural Pointset element.
		\item \textbf{GSTREF }- reference to a Structural Geomset element.
		\item \textbf{PARAM }- the component parameters, a list of values used in the Structural Pointset and Structural Geomset to define the Component.
		\item \textbf{GTYPE }- a word attribute indicating the generic type of the Profile. Any word value may be used. The following are suggested:
	\end{itemize}
	
	BEAM - beam
	
	BRAC - brace
	
	COLU - column
	
	GANT - gantry
	
	GIRD - girder
	
	JOIS - joist
	
	PILE - pile
	
	PROF - profile
	
	PURL - purlin
	
	RIDG - ridge
	
	SDRA - side rail
	
	\begin{itemize}
		\item \textbf{DTREF }- reference to a Dataset element.
	\end{itemize}
	
	\subsubsection{Joint (JOIN; SJOI)}
	\label{para:joint}
	The attributes of a Joint are:
	
	\begin{itemize}
		\item \textbf{PSTREF }- reference to a Structural Pointset element.
		\item \textbf{PTREF }- reference to a 3D Pointset element.
		\item \textbf{GMREF }- reference to a 3D Geomset element.
		\item \textbf{PARAM }- the component parameters, a list of values used in the Structural Pointset, 3D Pointset and 3D Geomset to define the Component.
		\item \textbf{GTYPE }- a word attribute indicating the generic type of the Joint. Any word value may be used. The following are suggested:
	\end{itemize}
	BASE - base
	
	JOIN - joint
	
	KNEE - knee
	
	\begin{itemize}
		\item \textbf{CTYA }- a word attribute indicating how the Joint is fixed to the attached Section (the Joint's \textbf{connection type }for the attached Section). Any word value may be used. If the connection type attribute of the attached Section (CTYS or CTYE) has not been set when the Joint is selected in the design process, the attribute will automatically be set to the value of CTYA. The PDMS data consistency checks (see the \textit{DESIGN Reference Manual}) check whether the connection type attributes of the Joint and attached Section match.
		\item \textbf{CTYO }- similar to CTYA, but for the Joint's owning Section (secondary Joints only).
		\item \textbf{DTREF }- reference to a Dataset element.
	\end{itemize}
	
	\subsubsection{Fitting (FITT; SFIT)}
	\label{para:fitting}
	The attributes of a Fitting are:
	
	\begin{itemize}
		\item \textbf{PTREF }- reference to a 3D Pointset element.
		\item \textbf{GMREF }- reference to a 3D Geomset element.
		\item \textbf{PARAM }- the component parameters, a list of values used in the Structural Pointset, 3D Pointset and 3D Geomset to define the Component.
		\item \textbf{GTYPE }- a word attribute indicating the generic type of the Fitting. Any word value may be used, but the word FITT is suggested.
		\item \textbf{CTYA }- a word attribute used only if the Fitting is attached to a pipe hanger in the Design DB. Any word value may be used. If the connection type attribute of the pipe hanger (HCON or TCON) has not been set when the Fitting is selected in the design process, the attribute will automatically be set to the value of CTYA. The PDMS data consistency checks (see the \textit{DESIGN Reference Manual}) check whether the connection type attributes of the Fitting and pipe hanger match.
		\item \textbf{DTREF }- reference to a Dataset element.
	\end{itemize}
	
	\textbf{NOTE: }For details of the \textbf{MODEL SETTINGS }command syntax 
	used to set default values for component parameters, and specimen values for 
	other classes of parameter, see Section 6.4.1.
	
	\begin{enumerate}
		\item \textbf{Navigating in the Catalogue Database Hierarchy}
	\end{enumerate}
	
	There are many ways in which you can explore the contents of the Catalogue 
	database, but they fall into three broad categories:
	
	\begin{itemize}
		\item Accessing a Catalogue element whose identity or hierarchical position is known
		\item Accessing a Catalogue element whose position in the hierarchy relative to the current position is known
		\item Accessing a Catalogue element by picking it from the screen
	\end{itemize}
	
	It is important to appreciate that these navigation facilities provide you 
	with access to the complete Catalogue and not just those items shown on the 
	graphical display.
	
	\subsection{Accessing a Catalogue Element on the Screen}
	\label{subsubsec:accessing}
	In graphical form, you can jump straight to an element which is shown in the 
	screen display by positioning the cursor over the element and pressing the 
	left-hand mouse button. This identifies the item under the cursor and makes 
	it the \textbf{current element}.
	
	Alternatively, the cursor can be used in the \textbf{Members }menu (or the 
	command window) to pick a name from the text display.
	
	\subsection{Accessing a Catalogue Element by Name}
	\label{subsubsec:mylabel9}
	You can jump straight to a known element simply by typing its name. You 
	would usually name an element when you create it.
	
	\subsection{Accessing an Element by Reference Number}
	\label{subsubsec:mylabel10}
	All elements are automatically given a reference number when created. By 
	stating this reference it is possible to access an unnamed element. 
	Reference numbers are not normally shown in PARAGON, but may be obtained by 
	the using the \textbf{Q REF }command.
	
	\subsection{Going to the Previously Accessed Element}
	\label{subsubsec:going}
	\textbf{Keywords: }\textbf{SAME CE}
	
	\textbf{Description: }\textbf{SAME }takes you to the element you were at 
	before you accessed the current element. Repeating the \textbf{SAME }command 
	has the effect of moving repeatedly between two items - it does not move 
	back along the list of items accessed.
	
	If the previously accessed element has been deleted, the \textbf{SAME}
	
	command will output an error message.
	
	\textbf{Example:}
	
	\textbf{CE }takes you to the current element itself. (This facility may seem 
	rather pointless in this situation; however the \textbf{CE }keyword is used 
	in many commands as a means of identifying an element to be the object of 
	that command.)
	
	\textsf{ADD CE }- Add the current element to the display.
	
	\textbf{Command Syntax:}
	
	\textsf{\textgreater -- CE --\textgreater }
	
	\textsf{\textgreater -- SAMe --\textgreater }
	
	\subsection{Ascending the Catalogue Hierarchy}
	\label{subsubsec:ascending}
	\textbf{Keywords: }\textbf{OWNER END}
	
	\textbf{Description: }Moving up the hierarchy involves fewer decisions than 
	moving downwards, as any element can have only one Owner. Two commands 
	(\textbf{OWNER }and \textbf{END}) allow you to move up to the immediate 
	parent.
	
	\textbf{END }differs from \textbf{OWNER }by allowing you to return to a 
	\textbf{Group }element from which the current element was accessed. As the 
	Group does not own that element, the command \textbf{OWNER }would go to the 
	element's true Owner and not the Group.
	
	It is possible to ascend the hierarchy in more than one step, by inputting 
	the type of element you wish to access. For example, to navigate from a 
	Piping Component to its Section would involve two successive \textbf{END 
	}commands (if a Category exists). However the command \textbf{SECT }would 
	have the effect of scanning up the hierarchy to find the Section which owns 
	that list, thus saving an \textbf{END }command.
	
	\textit{Navigating in the Catalogue Database Hierarchy}
	
	\subsection{Accessing an Element via a Reference Pointer}
	\label{subsubsec:mylabel11}
	\textbf{Keywords: }\textbf{GOTO}
	
	\textbf{Description: }Many elements have \textbf{reference attributes }whose 
	settings point to associated elements. The latter (referenced) elements hold 
	data which forms part of the definition of the original (referencing) 
	element. For example, the geometric definition of a catalogue component is 
	held in a GMSET (geometry set) element which is pointed to by the setting of 
	the component's GMREF attribute (see Chapter 7).
	
	The \textbf{GOTO }command allows you to navigate directly to a referenced 
	element by specifying the corresponding reference attribute of the current 
	element.
	
	\textbf{Examples:}
	
	\textsf{GOTO PTREF }goes to the PTSET specified by the PTREF setting
	
	\textsf{GOTO GMREF }goes to the GMSET specified by the GMREF setting
	
	\textbf{Command Syntax:}
	
	\textsf{\textgreater -- GOTO -- \textless refatt\textgreater --\textgreater 
	}
	
	where \textsf{\textless refatt\textgreater }is the name of any reference 
	attribute of the current element whose setting points to another element.
	
	\subsection{Other Navigation Commands}
	\label{subsubsec:other}
	\textbf{Keywords: }\textbf{FIRST LAST NEXT PREVIOUS MEMBER END TYPE}
	
	\textbf{Description: }Most of the above commands can be linked together with 
	the \textbf{OF}
	
	\begin{center}
		keyword to produce general navigation commands.
	\end{center}
	
	\textbf{Examples:}
	
	\textsf{FIRST SECT OF CATA /PIPECATA LAST PTSE OF PREVIOUS 3 SECT FIRST SCOM 
		OF /CATE 5}
	
	\textbf{Command Syntax:}
	
	(See \textsf{\textless gid\textgreater }syntax in Section 2.1.3.)
	
	\section{Component Design and Representation}
	\label{sec:component}
	This chapter introduces the methods of Component design and graphical 
	representation in PARAGON; in particular the \textbf{MODEL, MODEL SETTINGS 
	}and \textbf{REPRESENTATION }commands are detailed.
	
	\subsection{Component Design}
	\label{subsubsec:component}
	Assuming that you have opened a suitable 3D view, the interactive graphical 
	Component design process in PARAGON is initiated using the \textbf{MODEL 
	}command.
	
	If a new Component is to be designed, then a new catalogue element must 
	first be specified by a command such as
	
	\textbf{NEW SCOM /CR2-1 }(at SECT or CATE level)
	
	or
	
	\textbf{NEW SPRF /UB4-A }(at STSEC or STCAT level)
	
	The command
	
	\textbf{MODEL CE}
	
	(for `Model Current Element') will add the new component to the 3D view.
	
	Note that the \textbf{MODEL CE }command is valid only for SCOM, SPRF, JOIN, 
	and SFIT elements.
	
	Only complete Components may be displayed in this way - individual Pointsets 
	and Geomsets may not be, although these items will easily be 
	distinguishable. (Geomset and/or Pointset elements \textit{can }be removed from the 
	display with the aid of the \textbf{REPRESENTATION }command - see next 
	section).
	
	The \textbf{MODEL SETTINGS }command can be used to specify the Component 
	Design Data attributes. For example,
	
	\textsf{MODEL SETTINGS DDRADIUS 75 DDHEIGHT 200}
	
	gives the Design Data attributes DDRADIUS and DDHEIGHT values of 75mm and 
	200mm respectively. The DDRADIUS, DDHEIGHT and DDANGLE attributes are the 
	Design parameters used in the selection process for variable Components. In 
	PARAGON it is possible to use these attributes as part of the Component 
	design. For example, whereas an attribute such as PHEIGHT would normally be 
	defined in terms of parameters, a command such as
	
	\textsf{PHEI DDHEIGHT}
	
	(assuming a suitable current element) would set PHEIGHT to the Design 
	height. (In such a case, a \textbf{MODEL SETTINGS }command would need to be 
	followed by a \textbf{MODEL CE }command before any change in the display 
	would be observed.)
	
	To produce a display of a Component with insulation, the bore, temperature 
	and working pressure of the Component must be known. To this end the 
	\textbf{MODEL SETTINGS }command can be used to set the BORE, TEMP and 
	PRESSURE. This must be done before the Insulation Specification, INSPEC, can 
	be specified. For example,
	
	\textsf{MODEL SETTINGS TEMP 300 BORE 80}
	
	would set the temperature and bore Design Data attributes (the pressure 
	would stay at its default value, see below). The Insulation Spec may then be 
	specified by a command such as
	
	\textsf{MODEL SETTINGS INSPEC /INSUL1}
	
	Assuming the drawing REPRESENTATION (see Section 6.4) is correctly set, the 
	Component will then be displayed with insulation shown.
	
	All Design settings can be restored to their defaults by
	
	\textbf{MODEL SETTINGS DEFAULT}
	
	\textbf{NOTE: }This command also deletes all default and specimen values of 
	parameters. It unsets the Insulation Specification.
	
	The default values of the Design Data attributes, and the full syntax of how 
	to set them, are given in Section 6.4.
	
	\textbf{QUERY MODEL SETTINGS }will output the Design settings currently in 
	use. The Design process is turned off by
	
	\textbf{MODEL END}
	
	which also has the effect of clearing the display.
	
	\subsection{P-point and P-line Representation}
	\label{subsubsec:mylabel12}
	\subsubsection{P-points}
	\label{para:mylabel4}
	P-points may be displayed in PARAGON in one of two ways. The form of display 
	is controlled by the \textbf{REPRESENTATION PPOINTS }command as illustrated 
	in Figure 6-1.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=18.39in,height=5.24in]{Paragon9}}
		\label{fig9}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 6-1 }Specifying P-points On or Off
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.29in,height=2.00in]{Paragon10}}
		\label{fig10}
	\end{figure}
	
	The size of the arrow may also be controlled by the \textbf{REPRESENTATION 
		PPOINTS }command, as illustrated in Figure 6-2. The overall length of the 
	arrow is specified in millimetres. The default length is 50mm. Specifying a 
	length of zero causes the P-point to appear as a dot.
	
	\begin{center}
		\textbf{Figure 6-2 }Specifying P-point Length
	\end{center}
	
	The P-point numbers may be omitted, or they may be displayed any size, the 
	size being specified in millimetres. The default size is 5 mm. The size of 
	the numbers is controlled by the \textbf{REPRESENTATION PPOINTS }command, as 
	illustrated in Figure 6-3.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=18.40in,height=10.96in]{Paragon11}}
		\label{fig11}
	\end{figure}
	
	\textbf{Figure 6-3 }Specifying P-point Number Representation
	
	Both \textbf{LENGTH }and \textbf{NUMBERS }may be set in the same command, 
	for example:
	
	\textsf{REPRESENTATION PPOINTS ON LENGTH 25 NUMBERS ON SIZE 7}
	
	\textbf{NOTE: }P-points are always displayed in some form. They cannot be 
	omitted from the display completely.
	
	See the Reference Section at the end of this chapter for the full syntax of 
	the
	
	\textbf{REPRESENTATION PPOINTS }command.
	
	\subsubsection{P-lines}
	\label{para:mylabel5}
	P-lines may be displayed in PARAGON in one of two ways. The form of display 
	is controlled by the \textbf{REPRESENTATION PLINES }command as illustrated 
	in Figure 6-4.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=18.33in,height=5.19in]{Paragon12}}
		\label{fig12}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 6-4 }Specifying P-lines On or Off
	\end{center}
	
	The P-line identifier keys may be omitted or displayed. This is also 
	controlled by the
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.25in,height=3.60in]{Paragon13}}
		\label{fig13}
	\end{figure}
	
	\textbf{REPRESENTATION PLINES }command, as illustrated in Figure 6-5.
	
	\begin{center}
		\textbf{Figure 6-5 }Specifying P-line Identifier Key Representation
	\end{center}
	
	P-line length (default 50mm) and size (default 5mm) can also be controlled. 
	See the Reference Section at the end of this chapter for the full syntax of 
	the \textbf{REPRESENTATION PLINES }command.
	
	Unlike P-points, P-lines can be omitted from the display completely. Whether 
	a P-line is drawn or not depends on the settings of three of its attributes:
	
	\begin{itemize}
		\item LEVEL - the drawing level range
		\item CLFLA - the centreline drawing flag attribute
		\item TUFLA - the tube drawing flag attribute
	\end{itemize}
	LEVEL is a pair of integers. CLFLA and TUFLA are logical attributes which 
	are set to TRUE or FALSE (corresponding to `ON' or `OFF' respectively). When 
	you first create a P-line, CLFLA and TUFLA are both FALSE.
	
	Control is initially on the setting of LEVEL. If the PARAGON LEVEL 
	\textbf{setting }is within the LEVEL \textbf{range }specified for the P-line 
	(as its LEVEL attribute) then the P-line will be considered for drawing, 
	otherwise it will not be. If the level condition is satisfied, then whether 
	a P-line is displayed or not in PARAGON depends upon the settings of its 
	CLFLA and TUFLA attributes \textit{and }upon the settings of the \textbf{drawing options 
	}specified by the \textbf{REPRESENTATION }command.
	
	The \textbf{REPRESENTATION }command provides a means of effectively 
	overriding the settings of the P-line's drawing attributes \textit{without }changing them. An 
	example \textbf{REPRESENTATION }command is
	
	\textsf{REPRESENTATION TUBE ON CL OFF}
	
	(The word \textsf{CENTRELINE }may be used instead of \textsf{CL}.)
	
	The drawing option settings interact with the drawing attributes of the 
	P-lines thus: if an `ON' REPRESENTATION setting matches a corresponding 
	`TRUE' attribute setting (e.g. \textsf{REPRESENTATION CL ON }and 
	\textsf{CLFL TRUE}) then the P-line will be drawn, otherwise it will not be 
	drawn.
	
	The drawing of Geomset primitives is controlled in a similar way. The next 
	section gives examples of how the LEVEL, CLFLA and TUFLA attributes interact 
	with the REPRESENTATION settings.
	
	\subsection{Geomset Primitive Representation}
	\label{subsubsec:geomset}
	Whether a Geomset primitive is displayed or not depends on the settings of 
	its LEVEL, CLFLA and TUFLA attributes (as for a P-line) and also on its OBST 
	attribute. (The OBST attribute is a number which defines the degree of 
	obstruction for clash checking.)
	
	If the PARAGON LEVEL setting is within the LEVEL range specified for the 
	primitive (as its LEVEL attribute), then the primitive will be considered 
	for drawing, otherwise it will not be. If the level condition is satisfied 
	then, the primitive will be displayed if it has an OBST value of 1 or 2 and 
	the REPRESENTATION setting is
	
	\textsf{REPRESENTATION OBSTRUCTIONS ON}
	
	The primitive will be drawn in solid lines if OBST $=$ 2 (hard obstruction), 
	dashed lines if OBST $=$ 1 (soft obstruction0.
	
	The control mechanisms of tube, centreline and obstruction are quite 
	independent of each other. So, for example, if a primitive has an OBST value 
	of 2 and the REPRESENTATION setting is OBSTRUCTIONS ON, the primitive will 
	be drawn whatever the values of its CLFLA and TUFLA attributes and the 
	REPRESENTATION
	
	TUBE and CL settings (provided that the PARAGON LEVEL setting is within the 
	LEVEL range of the primitive).
	
	\textbf{NOTE: }Whenever you use a \textbf{REPRESENTATION }command, the 
	current design Component is redrawn. If you want to change several 
	REPRESENTATION settings, put them all in the same line so that the Component 
	is only redrawn once. For example,
	
	\textsf{REPRESENTATION TUBE ON CL OFF OBST ON PPOINTS OFF}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.18in,height=4.89in]{Paragon14}}
		\label{fig14}
	\end{figure}
	
	The following example shows the Catalogue representation of a control valve, 
	and how it might appear in PARAGON with various combinations of TUBE, CL and 
	OBST settings. All the illustrations have PPOINTS ON.
	
	\textbf{Figure 6-6 }Catalogue Control Valve, showing all Primitives For this 
	example, the settings of the attributes of interest are considered to be:
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{32pt}|l|l|l|l|l|}
				\hline
				\textsf{SCYL}& 
				\textsf{1}& 
				\textsf{- OBST}& 
				\textsf{2,}& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL FALSE} \\
				\hline
				\textsf{SCYL}& 
				\textsf{2}& 
				\textsf{- OBST}& 
				\textsf{2,}& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL FALSE} \\
				\hline
				\textsf{SSPH}& 
				\textsf{1}& 
				-\textsf{ OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{TRUE, TUFL TRUE} \\
				\hline
				\textsf{SCON}& 
				\textsf{1}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{TRUE, TUFL TRUE} \\
				\hline
				\textsf{SDSH}& 
				\textsf{1}& 
				\textsf{- OBST}& 
				\textsf{2,}& 
				\textsf{CLFL}& 
				\textsf{TRUE, TUFL TRUE} \\
				\hline
				\textsf{SCYL}& 
				\textsf{3}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL TRUE} \\
				\hline
				\textsf{SCYL}& 
				\textsf{4}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL TRUE} \\
				\hline
				\textsf{LSNO}& 
				\textsf{1}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL TRUE} \\
				\hline
				\textsf{LSNO}& 
				\textsf{2}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{TRUE, TUFL FALSE} \\
				\hline
				\textsf{LSNO}& 
				\textsf{3}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{FALSE, TUFL TRUE} \\
				\hline
				\textsf{LSNO}& 
				\textsf{4}& 
				\textsf{- OBST}& 
				0,& 
				\textsf{CLFL}& 
				\textsf{TRUE, TUFL FALSE} \\
				\hline
			\end{tabular}
			\label{tab11}
		\end{center}
	\end{table}
	
	SCYL 1, SCYL 2 and SDSH 1 are \textbf{obstruction volume primitives}, that 
	is, they represent the obstruction volume of the Component, not its physical 
	geometry and dimensions. The other primitives represent the actual geometry 
	and dimensions of the Component.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.35in,height=4.62in]{Paragon15}}
		\label{fig15}
	\end{figure}
	
	The following illustrations show the appearance of the Component under 
	various REPRESENTATION settings.
	
	\textbf{Figure 6-7 }REPRESENTATION OBST OFF TUBE OFF CL ON
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.18in,height=4.89in]{Paragon16}}
		\label{fig16}
	\end{figure}
	
	This is the default REPRESENTATION setting for OBSTRUCTION, TUBE and 
	CENTRELINE. The attribute settings chosen for this example are `typical' for 
	a Catalogue, and so Figure 6-7 shows the `normal' appearance of the valve. 
	Notice how the OBST OFF setting does not affect the visibility of the 
	obstruction dish (handwheel space) since it has CLFL TRUE.
	
	\begin{center}
		\textbf{Figure 6-8 }REPRESENTATION OBST ON TUBE OFF CL ON
	\end{center}
	
	Here the OBST ON setting matches the OBST 2 attribute value of the 
	obstruction cylinders and so they become visible, even though they have CLFL 
	and TUFL both FALSE.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.17in,height=13.62in]{Paragon17}}
		\label{fig17}
	\end{figure}
	
	\textbf{Figure 6-9 }REPRESENTATION OBST ON TUBE OFF CL OFF
	
	Here TUBE and CENTRELINE are both OFF but OBST is ON, and so only the 
	obstruction volume primitives are visible.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.17in,height=13.60in]{Paragon18}}
		\label{fig18}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 6-10 }REPRESENTATION OBST ON TUBE ON CL OFF
	\end{center}
	
	Compared with Figure 6-9, those primitives with TUFL TRUE now become visible 
	because TUBE is now ON. The obstruction primitives remain visible because 
	OBST is still ON.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.15in,height=13.59in]{Paragon19}}
		\label{fig19}
	\end{figure}
	
	\textbf{Figure 6-11 }REPRESENTATION OBST OFF TUBE ON CL OFF
	
	OBST is now OFF and so the obstruction cylinders disappear. (The obstruction 
	dish remains because it has TUFL TRUE.)
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.17in,height=13.60in]{Paragon20}}
		\label{fig20}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 6-12 }REPRESENTATION OBST OFF TUBE ON CL ON
	\end{center}
	
	Here, all those primitives which have one or both of CLFL, TUFL TRUE are 
	visible.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.17in,height=13.59in]{Paragon21}}
		\label{fig21}
	\end{figure}
	
	\textbf{Figure 6-13 }REPRESENTATION OBST ON TUBE ON CL ON
	
	In Figure 6-13, all the REPRESENTATION settings are ON and so all the 
	Geomset primitives are visible.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.16in,height=13.59in]{Paragon22}}
		\label{fig22}
	\end{figure}
	
	\textbf{Figure 6-14 }REPRESENTATION OBST OFF TUBE OFF CL OFF
	
	Here, all the REPRESENTATION settings are OFF and so no primitives are 
	visible. The Component P-points are still visible since the REPRESENTATION 
	PPOINTS setting in the example is ON.
	
	The full default REPRESENTATION is:
	
	\textsf{CL ON TUBE OFF}
	
	\textsf{OBSTRUCTIONS OFF LEVEL 0}
	
	\textsf{PPOINTS ON LENGTH 50 NUMBERS OFF PLINES ON PKEYS OFF}
	
	which is regained by
	
	\textbf{REPRESENTATION DEFAULT}
	
	Note that the TVISIBLE and BVISIBLE end visibility flags have no effect in 
	PARAGON.
	
	\subsection{Reference Section}
	\label{subsubsec:reference}
	This section gives the syntax of the \textbf{MODEL SETTINGS }command and the 
	\textbf{REPRESENTATION }command, as described in this chapter and in Chapter 
	4 (the latter for setting component parameter defaults etc.).
	
	The description of the syntax for the \textbf{REPRESENTATION }command is 
	spread over a number of separate sections, each showing how the command is 
	applied to a particular type of element. The final section summarises the 
	complete \textbf{REPRESENTATION }syntax in a single diagram.
	
	Querying information is given, as are further examples, where appropriate.
	
	\subsubsection{Model Settings}
	\label{para:model}
	\textbf{Keywords: }\textbf{MODEL SETTINGS}
	
	\textbf{Function}: Sets default component parameters and design data 
	attributes.
	
	\textbf{Description}: Sets default values for component parameters and 
	specimen values for other classes of parameters (see Chapter 4). Also sets 
	design data attributes; the numeric attributes may be used in place of 
	parameters for defining Pointsets and Geomsets.
	
	\textbf{Examples of setting default component parameters}:
	
	\textsf{MODEL SET PAR 3 35 }Sets default value for component parameter 3 to 
	35
	
	\textsf{MODEL SET IPAR 1 3.5 IPAR 2 4.5 }Sets insulation parameter 1 to 3.5
	
	and insulation parameter 2 to 4.5
	
	\textsf{MODEL SET APAR 1 250 }Sets attached parameter 1 to 250
	
	\textsf{MODEL SET APAR 3 5.1 OPAR 2 19.75 }Sets attached parameter 3 to 5.1
	
	and owning parameter 2 to 19.75
	
	\textsf{MODEL SET CAT OPAR 3 2.5 }Sets owning parameter 3 to 2.5
	
	\textsf{MODEL SET DES PARA 3 1.2 }Sets design parameter 3 to 1.2
	
	\textsf{MODEL SET DES APAR 10 99 }Sets design attached parameter 10 to 99
	
	\textsf{MODEL SET DES PAR 2 (ATAN(4 / 3)) }Sets design parameter 2 to 
	tan$^{-1\, }$4/3
	
	\textsf{MODEL SET DEF }Deletes all default and specimen parameters (also 
	sets Design Data attributes to default values)
	
	The word CAT (short for CATALOGUE) in the fifth example is optional. You can 
	use it when setting default values for component parameters, and when 
	setting specimen values for structural parameters. You may find it helpful 
	to use the word for clarity in macros, to distinguish between Design DB 
	parameters and other classes of parameters.
	
	Values for any of these classes of parameters may be set in a single 
	command, for example:
	
	\textsf{MODEL SET PAR 2 12 IPAR 1 17 APAR 2 32 DES PAR 3 25 DES OPAR 5 6.3}
	
	\textbf{Examples of setting design data attributes}:
	
	\textsf{MODEL SET INSPEC /IS50 }Set Insulation Specification to IS50
	
	\textsf{MODEL SET BOR 100 TEMP 350 PRESS 50}
	
	Set Component bore, temperature and pressure to given Design values
	
	\textsf{MODEL SET DDHEI 2000 DDRAD 35}
	
	Set height and radius to given Design values
	
	\textsf{MODEL SET DDANG (ASIN(6 / 7)) }Set Design Angle to arcsin (6/7)
	
	\textsf{MODEL SET DEF }Set Design Data attributes to default values (also 
	deletes all default and specimen parameters and unsets Insulation Spec)
	
	\textbf{Default values}:
	
	\textsf{TEMP }-100000
	
	\textsf{BORE }150.0 mm
	
	\textsf{PRESSURE }.
	
	\textsf{DDANGLE }90 degrees
	
	\textsf{DDHEIGHT }100.0 mm
	
	\textsf{DDRADIUS }225 mm
	
	\textsf{INSPEC }Nulref (i.e. unset)
	
	\textbf{Command Syntax}:
	
	\begin{flushright}
		\textsf{.---------------------\textless ------------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\textsf{\textgreater - MODEL - SETtings --}$+$\textsf{--*- CATalogue* }-. 
	\textsf{\textbar }
	
	\textsf{\textbar \textbar - DESign -----\textbar \textbar }
	
	\textsf{\textbar \textbar --------------}$+$\textsf{- PARam }--. 
	\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar - APARam -\textbar \textbar }
	
	\textsf{\textbar \textbar `- OPARam -}$+$ \textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar - IPARam ----------------}$+$\textsf{------. 
		\textbar }
	
	\textsf{\textbar \textbar .-------------' \textbar }
	
	\textsf{\textbar \textbar `- }\textsf{\textit{number 
	}}\textsf{-}$+$\textsf{- }\textsf{\textit{value }}\textsf{\textbar }
	
	\textsf{\textbar \textbar `- \textless expres\textgreater -\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- INSpec }---\textsf{ }\textsf{\textit{name 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- TEMp }---\textsf{ }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- BORe }---\textsf{ }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PREssure }---\textsf{ }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- DDHEIght }---\textsf{ }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- DDRADius }---\textsf{ }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar `-- DDANGle ---}$+$\textsf{--- }\textsf{\textit{value 
	}}\textsf{\textbar }
	
	\textsf{\textbar `--- \textless expres\textgreater \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`--- DEFault 
		--------------------------------}$+$\textsf{--\textgreater }
	
	\textbf{Querying Syntax}:
	
	\textsf{\textgreater - Q - MODEL -- SETtings --}$+$\textsf{-- CATalogue }--.
	
	\textsf{\textbar -- DESign \textbar }
	
	\textsf{\textbar ---------------}$+$\textsf{-- PARam }---.
	
	\textsf{\textbar \textbar -- APARam --\textbar }
	
	\textsf{\textbar `-- OPARam --}$+$
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- IPARam \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- INSpec \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- TEMp \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- BORe \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- PREssure \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- DDHEIght \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- DDRADius \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- DDANGle -----------------}$+$\textsf{--\textgreater }
	
	\subsubsection{Setting Representation for Piping Components}
	\label{para:setting}
	\textbf{Keywords: }\textbf{REPRESENTATION TUBE CL CENTRELINE}
	
	\textbf{Description: }The \textbf{REPRESENTATION }command allows piping 
	components to be represented by a single centreline (CL) or by a 2D outline 
	(TUBE). In some cases, it helps to switch between the two representations to 
	simplify an otherwise complicated view.
	
	\begin{center}
		Switching TUBE On switches CL Off automatically, and vice versa.
	\end{center}
	
	\textbf{Examples:}
	
	TUBE and CL representations are not instantly updated on the screen. To see 
	the effects of a representation change, it is necessary to replace the 
	affected item in the Draw List by Removing and Adding it.
	
	\textsf{REPR TUBE ON }Sets tubing representation as double line
	
	\textsf{REPR CL ON }Sets tubing representation as centreline
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{.---------------------\textless -----------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --*-- CL }-------------------------. 
		\textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- CENTreline -----------------\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`-- TUBE -----------------------}$+$\textsf{-- ON ---\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`-- OFF --}$+$\textsf{--\textgreater }
	\end{flushright}
	
	\textbf{Querying:}
	
	\textsf{Q REPR TUBE Q REPR CL}
	
	\textsf{Q REPR }- queries all Representation options.
	
	\subsubsection{Setting Profile Representation for Steelwork}
	\label{para:mylabel6}
	\textbf{Keywords: }\textbf{REPRESENTATION PROFILE}
	
	\textbf{Description: }The \textbf{REPRESENTATION PROFILE }commands allow 
	structural steel profiles to be represented by a single centreline or by a 
	2D outline. In some cases, it helps to switch between the two 
	representations to simplify an otherwise complicated view.
	
	\textbf{Examples:}
	
	Changes to the representation are not instantly updated on the screen. To 
	see the effects of a representation change, it is necessary to replace the 
	affected item in the Draw List by Removing and Adding it.
	
	\textsf{REPR PROF ON PROF CL OFF }Sets profile representation as 2D outline 
	\textsf{REPR PROF CL ON PROF OFF }Sets profile representation as centreline 
	\textsf{REPR PROF ON PROF CL ON }Sets both types of representation on
	
	\begin{flushright}
		\textsf{.-----------------\textless --------------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --*-- PROFile --}$+$\textsf{-- CL 
		}----------. \textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- CENTreline --\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`----------------}$+$\textsf{-- ON ---\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`-- OFF --}$+$\textsf{--\textgreater }
	\end{flushright}
	
	\textbf{Querying:}
	
	\textsf{Q REPR PROF}
	
	\textsf{Q REPR }- queries all Representation options.
	
	\subsubsection{Setting Level Representation}
	\label{para:mylabel7}
	\textbf{Keywords: }\textbf{REPRESENTATION LEVEL}
	
	\textbf{Description: }This command enables individual drawing levels to be 
	specified for the display of catalogue elements. Every basic primitive shape 
	has an associated drawing level range attribute stored in the Catalogue. If 
	the specified drawing level coincides with this range, the 3D object will be 
	drawn when it is added to the Draw List.
	
	The practical effect of this facility is that it allows you to minimise 
	visible detail when representing catalogue items. For instance, at level 3, 
	steelwork may be represented as single line only, whereas at level 1 the 
	full detail may be visible. Level 3 may well be adequate for design 
	purposes.
	
	\textbf{Examples:}
	
	LEVEL manipulation is not instantly updated on the screen. To see the 
	effects of a level change, use the REPR UPDATE command.
	
	\textsf{REPR LEVEL PIPE 5 }Sets piping level to 5. All pipes which are added
	
	after this command will be drawn at level 5. Those which were already in the 
	view will remain unchanged.
	
	\textsf{REPR LEVEL 2 }Set level for all other Component types to 2
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{.-------------------\textless -------------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --*-- LEVel --}$+$\textsf{-- PIPE 
		}-------. \textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- NOZZle -----\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- STRUcture --\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{`---------------}$+$\textsf{-- }\textsf{\textit{integer 
	}}\textsf{--}$+$\textsf{--\textgreater }
	
	\textbf{Querying:}
	
	\textsf{Q REPR - }lists all REPRE options
	
	\textsf{Q REPR LEVEL - }lists levels at which other Components are drawn
	
	\textsf{Q DISPLAY }gives units and tolerance settings, as well as
	
	representation levels
	
	\subsubsection{Setting Obstruction and Insulation Representation}
	\label{para:mylabel8}
	\textbf{Keywords: }\textbf{REPRESENTATION OBSTRUCTION INSULATION}
	
	\textbf{Description: }Component Obstructions are often given LEVELS or TUBE 
	and CENTRELINE settings which render them invisible. Setting the 
	Representation of OBST On forces the system to override normal LEVEL and 
	TUBE settings and show all of the primitives, regardless of the other 
	settings.
	
	Setting the Representation of INSU On or Off determines whether or not 
	insulation is shown on primitives.
	
	\textbf{Examples:}
	
	These have the effect of considering all primitives which have an 
	obstruction level greater than zero and all primitives which are affected by 
	insulation parameters. As with changes to LEVEL representation, the graphics 
	display is not updated instantly. Use the RECR UPDATE command to make any 
	changes visible.
	
	\textsf{REPR OBST ON INSU OFF REPR INSU ON}
	
	\textsf{REPR PROF OBST ON PROF INSU OFF}
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{.--------------\textless ------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --*-- OBSTruction }--. 
		\textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- INSUlation ---}$+$ \textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`-- PROFile --}$+$\textsf{- OBSTruction -\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`- INSUlation --}$+$\textsf{- ON --.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`- OFF -}$+$\textsf{--\textgreater }
	\end{flushright}
	
	\textbf{Querying:}
	
	\textsf{Q REPR }Lists all Representation settings
	
	\textsf{Q REPR INSU }Queries if INSU is ON or OFF
	
	\textsf{Q REPR OBST }Queries if OBST is ON or OFF
	
	\subsubsection{Setting P-Point Representation}
	\label{para:mylabel9}
	\textbf{Keywords: }\textbf{REPRESENTATION PPOINTS LENGTH NUMBERS}
	
	\textbf{Description: }P-point representation may be set to ON or OFF. The 
	default setting is PPOINTS OFF, although p-points will be shown 
	automatically as part of an identification operation.
	
	When p-points are on, they are drawn as small arrows with a cross at the 
	p-point position and with the arrow indicating the p-point direction. The 
	size of the arrow is controlled by the LENGTH option. P-point numbers may 
	also be displayed, as controlled by the NUMBERS option.
	
	\textbf{Examples:}
	
	As with changes to other representation settings, the graphics display is 
	not updated instantly. Items must be removed and re-added to the Draw List 
	before changes to the display of p-points becomes visible.
	
	\textsf{REPR PPOINTS ON }Sets the p-point representation to ON
	
	\textsf{REPR PPOINTS LENGTH 5 }Sets size of p-point arrows
	
	\textsf{REPR PPOINTS NUMB ON }Shows p-point numbers
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation - PPoints --}$+$\textsf{-- ON }---.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar -- OFF --\textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`---------}$+$\textsf{-- LENgth -- \textless uval\textgreater --.}
	
	\textsf{\textbar \textbar }
	
	\textsf{`----------------------}$+$\textsf{--.}
	
	\begin{flushright}
		\textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{.--------------\textless ---------------------'}
	\end{flushright}
	
	\textsf{\textbar }
	
	\textsf{}$+$\textsf{-- NUMbers --}$+$\textsf{-- ON }---.
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar `-- OFF --\textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-----------------------}$+$\textsf{--\textgreater }
	
	\textbf{Querying:}
	
	\textsf{Q REPR PPOINTS}
	
	\subsubsection{Setting P-Line Representation}
	\label{para:mylabel10}
	\textbf{Keywords: }\textbf{REPRESENTATION PLINES LENGTH PKEY}
	
	\textbf{Description: }P-line representation for structural Profiles may be 
	set to ON or OFF. The default setting is PLINES OFF.
	
	When p-lines are on, the size of the arrow showing their direction is 
	controlled by the LENGTH option. P-line identifiers, in the form of the 
	settings of their PKEY attributes (TOS, BOS, NA, etc.) may also be 
	displayed, as controlled by the PKEY option.
	
	\textbf{Examples:}
	
	As with changes to other representation settings, the graphics display is 
	not updated instantly. Use the RECR UPDATE command to see changes to the 
	display of p-lines.
	
	\textsf{REPR PLINES ON }Sets the p-line representation to ON
	
	\textsf{REPR PLINES LENGTH 6 }Sets size of p-line arrows
	
	\textsf{REPR PLINES PKEY ON }Shows p-line identifiers (settings of PKEY 
	attributes)
	
	\textbf{Command Syntax:}
	
	\begin{flushright}
		\textsf{.---------------------\textless ---------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --*-- PLINes -}$+$\textsf{- ON }--. 
		\textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar \textbar - OFF -\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar `-------}$+$\textsf{- LENgth - \textless uval\textgreater 
		-\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar `-------------------\textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- PKEYs --}$+$\textsf{- ON --. \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{`- OFF -}$+$ \textsf{}$+$\textsf{--\textgreater }
	
	\textbf{Querying:}
	
	\textsf{Q REPR PLINES Q REPR PKEYS}
	
	\subsubsection{The Full REPRESENTATION Syntax}
	\label{para:mylabel11}
	\begin{flushright}
		\textsf{.----------------------\textless -------------------.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{/ \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textgreater -- REPResentation --}$+$\textsf{--*-- TUBE }-\textsf{ 
			\textless onoff\textgreater \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar -- CL }----------. \textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar \textbar -- CENTreline --}$+$\textsf{- \textless 
		onoff\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- HOLEs }-\textsf{ \textless onoff\textgreater 
		\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- OBSTruction }-\textsf{ \textless 
		onoff\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- INSUlation }-\textsf{ \textless 
		onoff\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- LEVel -}$+$\textsf{- PIPE }------. 
	\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - NOZZle ----\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - STRUcture -\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar `-------------}$+$\textsf{- 
	}\textsf{\textit{integer }}\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PPoints - \textless onoff\textgreater 
	}-\textsf{ \textless ppsiz\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PROFile -}$+$\textsf{- CL }----------. 
	\textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - CENTreline --\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - OBSTruction -\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - INSUlation --\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar `---------------}$+$\textsf{- \textless 
		onoff\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PNODes }--.\textsf{ .--------\textless 
		---------. \textbar }
	
	\textsf{\textbar \textbar \textbar / \textbar \textbar }
	
	\textsf{\textbar \textbar -- SNODes --*- \textless onoff\textgreater 
		----------\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar \textbar - COLour - \textless colno\textgreater 
		-\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar `-- SIZe \textless uval-----}$+$ \textsf{\textbar 
	}
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- POINts }-\textsf{ \textless onoff\textgreater 
		\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PKEYs }-\textsf{ \textless onoff\textgreater 
		\textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- PLINes - \textless onoff\textgreater 
		-}$+$\textsf{- LENgth - \textless uval\textgreater }-. \textsf{\textbar }
	
	\begin{center}
		\textsf{\textbar \textbar \textbar \textbar \textbar }
	\end{center}
	
	\begin{center}
		\textsf{\textbar \textbar `-------------------}$+$\textsf{--\textbar }
	\end{center}
	
	\begin{center}
		\textsf{\textbar \textbar \textbar }
	\end{center}
	
	\begin{center}
		\textsf{Continued Continued}
	\end{center}
	
	\begin{center}
		\textsf{Continued Continued}
	\end{center}
	
	\begin{center}
		\textsf{\textbar \textbar -- HOLes }-\textsf{ \textless onoff\textgreater 
			\textbar }
	\end{center}
	
	\begin{center}
		\textsf{\textbar \textbar \textbar }
	\end{center}
	
	\begin{center}
		\textsf{\textbar \textbar -- MASSproperties }-\textsf{ \textless 
			int\textgreater \textbar }
	\end{center}
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- DARCtolerance }-\textsf{ \textless 
		uval\textgreater \textbar }
	
	\textsf{\textbar \textbar \textbar }
	
	\textsf{\textbar }$\backslash $\textsf{-- UPDATE \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- DEFault 
		------------------------------------}$+$\textsf{--\textgreater }
	
	\textless onoff\textgreater is either \textsf{ON }or \textsf{OFF}
	
	\textless ppsiz\textgreater is
	
	\begin{flushright}
		\textsf{\textgreater --}$+$\textsf{- LENgth - \textless uval\textgreater }-.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`-------------------}$+$\textsf{- NUMbers - \textless 
			onoff\textgreater .}
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{center}
		\textsf{`---------------------}$+$\textsf{--\textgreater }
	\end{center}
	
	\textless colno\textgreater is
	
	\begin{flushright}
		\textsf{\textgreater --}$+$\textsf{-- }\textsf{\textit{integer }}--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- ACTive \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- VISIble \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar -- CE \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- CLASH \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- OBST \textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar -- COMPAre --}$+$\textsf{-- MATCHed 
	}-----------------------. \textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- MISMatched --------------------\textbar 
		\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar -- UNMAtched --}$+$\textsf{-- CONNector }--. 
	\textsf{\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar \textbar \textbar }
	
	\textsf{\textbar \textbar `---------------}$+$\textsf{--\textbar \textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar `-- TEXT --------------------------}$+$\textsf{--\textbar }
	
	\textsf{\textbar \textbar }
	
	\textsf{`-- AIDS 
		-------------------------------------------}$+$\textsf{--\textgreater }
	
	\begin{enumerate}
		\item \textbf{Pointsets and Geomsets}
	\end{enumerate}
	
	This chapter describes in detail the following Catalogue DB elements:
	
	\begin{itemize}
		\item 3D Pointset (PTSET)
		\item Structural Pointset (PTSSET)
		\item 3D Geomset (GMSET)
		\item Negative 3D Geomset (NGMSET)
		\item Structural Geomset (GMSSET)
	\end{itemize}
	
	Creation and manipulation of the Catalogue elements is described in Chapter 
	8.
	
	\subsection{3D Pointsets (PTSET)}
	\label{subsubsec:mylabel13}
	A PTSET is a collection of P-point elements. P-points are used in the design 
	process to position and orientate Piping Components, and to define their 
	connectivity to each other. P-points may also be used in PARAGON to define 
	the position and orientation of the 3D Geomset primitives which make up 
	Piping Components, Joints and Fittings. (Profiles do not use P-points.)
	
	A P-point has a \textbf{3D position }and a \textbf{direction}, and is 
	identified by a \textbf{number}. Each PTSET includes a special P-point, 
	P-point zero (P0), whose position is the component origin and whose 
	direction is the Z axis direction of the Component. It has no other 
	attributes. P0 is created automatically by PARAGON; you cannot change it in 
	any way.
	
	The numbering of the P-points of Piping Components must follow certain 
	conventions - see Appendix A for a summary of these, and the \textit{ISODRAFT Reference Manual }for fuller 
	details. There are no special conventions for numbering the P-points of 
	Joints and Fittings.
	
	A P-point has a \textbf{connection type }attribute, which is used only when 
	the P-point belongs to a Piping Component. The connection type attribute can 
	be used to specify how a Piping Component is connected to another at the 
	position of the P-point, for example by a butt weld or socket weld.
	
	A P-point has a \textbf{bore }attribute, which is used only when the P-point 
	belongs to a Piping Component. It can be used to specify the bore of the 
	pipe at that point.
	
	PDMS's data consistency checks (see the \textit{DESIGN Reference Manual}) can be used to check that the 
	connection type attributes of Piping Components are compatible with the 
	corresponding attributes of the Components to which they are connected. The 
	compatibility of connection types is defined in a Connection Compatibility 
	Table (CCTAB) - see Section 9.3 for details.
	
	Use of the \textbf{REPRESENTATION }command affects how P-points are drawn by 
	PARAGON; see Section 6.2 for details.
	
	A PTSET has the following attributes:
	
	\begin{itemize}
		\item DESC - a textual description of the Pointset
		\item GTYP - the generic type of the item for which the Pointset is used
		\item SKEY - the Symbol Key to which the Pointset relates (see the
	\end{itemize}
	\begin{center}
		\textit{ISODRAFT Reference Manual})
	\end{center}
	
	\begin{itemize}
		\item PURP - the purpose of the Pointset
	\end{itemize}
	
	A PTSET may contain one or more of the three types of P-point element:
	
	\begin{itemize}
		\item \textbf{Axial }P-point - PTAXI
		\item \textbf{Cartesian }P-point - PTCAR
		\item \textbf{Mixed }P-point - PTMIX
	\end{itemize}
	
	\subsubsection{Axial P-point (PTAXI)}
	\label{para:axial}
	A PTAXI allows a P-point to be defined in terms of an \textbf{axis }and a 
	\textbf{distance }along that axis. A PTAXI has no member elements and has 
	the following attributes:
	
	\begin{itemize}
		\item NUMB - the P-point number
		\item PCON - the connection type
		\item PBOR - the bore of the P-point
		\item PAXI - the axis of the P-point
		\item PDIS - the distance along the axis of the P-point
		\item PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT
		\item DESC - a textual description of the P-point
		\item PURP - the purpose of the P-point
	\end{itemize}
	NUMB must be set as a value. PAXI must be set as a direction - see Section 
	8.5.2 for details. The other attributes may be set as values or words (as 
	appropriate), or in terms of parameters (which in turn are values or words). 
	The classes of parameter which may be used depend on the class of Component 
	(Piping Component, Joint or Fitting) which uses the P-point - see Section 
	4.7 for details. PCON and PBOR are used for Piping Components only. They 
	have no meaning if the P-point is used by a Joint or Fitting. For details of 
	PSKEY settings, see Section 8.5.8.
	
	These conventions also apply to the attributes of the PTCAR and PTMIX 
	elements described below. See Section 8.5 for examples of setting these 
	attributes.
	
	\subsubsection{Cartesian P-point (PTCAR)}
	\label{para:cartesian}
	A PTCAR allows a P-point to be defined by specifying its position and 
	direction explicitly. A PTCAR has no member elements and has the following 
	attributes:
	
	\begin{itemize}
		\item NUMB - the P-point number
		\item PCON - the connection type
		\item PBOR - the bore of the P-point
		\item PX,PY,PZ - the X, Y, Z coordinates of the P-point
		\item PTCDIR - the direction of the P-point
		\item PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT
		\item DESC - a textual description of the P-point
		\item PURP - the purpose of the P-point
	\end{itemize}
	PTCDIR must be set as a direction - see Section 8.5.5 for details.
	
	\subsubsection{Mixed Type P-point (PTMIX)}
	\label{para:mixed}
	A PTMIX allows a P-point to be defined by specifying the position explicitly 
	but using PAXI to specify the direction. A PTMIX has no member elements and 
	has the following attributes:
	
	\begin{itemize}
		\item NUMB - the P-point number
		\item PCON - the connection type
		\item PBOR - the bore of the P-point
		\item PX,PY,PZ - the X, Y, Z coordinates of the P-point
		\item PAXI - the axis of the P-point
		\item PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT
		\item DESC - a textual description of the P-point
		\item PURP - the purpose of the P-point
	\end{itemize}
	
	\subsubsection{Position Type P-point (PTPOS)}
	\label{para:position}
	A PTPOS allows a P-point to be defined by specifying a position expression 
	PTCPOS and using PTCD to specify the direction expression. A PTPOS has no 
	member elements and has the following attributes:
	
	\begin{itemize}
		\item NUMB - the P-point number
		\item PCON - the connection type
		\item PBOR - the bore of the P-point
		\item PTCPOS - the position expression
		\item PTCD - the direction expression
		\item PSKEY - the pipe fitting (end condition) type to be used by ISODRAFT
		\item DESC - a textual description of the P-point
		\item PURP - the purpose of the P-point.
	\end{itemize}
	
	\subsection{Structural Pointsets (PTSSET)}
	\label{subsubsec:structural}
	A PTSSET is a collection of P-line elements (PLINE). P-lines are used in the 
	Catalogue by Profiles and Joints. P-lines are used in the design process to 
	position and orientate Sections (derived from Profiles) and Joints.
	
	Direction of P-line
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.96in,height=0.79in]{Paragon23}}
		\label{fig23}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.27in,height=0.17in]{Paragon24}}
		\label{fig24}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.15in,height=0.14in]{Paragon25}}
		\label{fig25}
	\end{figure}
	
	Position of P-line
	
	\begin{center}
		Y
	\end{center}
	
	PROFILE
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.17in,height=0.15in]{Paragon26}}
		\label{fig26}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.15in,height=0.17in]{Paragon27}}
		\label{fig27}
	\end{figure}
	
	\begin{center}
		X
	\end{center}
	
	(viewing in
	
	-Z direction)
	
	Direction of P-line
	
	Position of P-line
	
	\begin{flushright}
		Y
	\end{flushright}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.02in]{Paragon28}}
		\label{fig28}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.17in,height=0.15in]{Paragon29}}
		\label{fig29}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.17in,height=0.17in]{Paragon30}}
		\label{fig30}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.17in,height=0.16in]{Paragon31}}
		\label{fig31}
	\end{figure}
	
	\begin{flushright}
		X
	\end{flushright}
	
	SECTION $^{Z}$
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.90in,height=1.15in]{Paragon32}}
		\label{fig32}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.13in,height=0.14in]{Paragon33}}
		\label{fig33}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.23in,height=0.21in]{Paragon34}}
		\label{fig34}
	\end{figure}
	
	\textbf{Figure 7-1 }2D and 3D Views of a P-line
	
	A P-line is the structural counterpart of a P-point. It is a line which runs 
	the full length of a Component parallel to its Z axis. Viewed in the XY 
	plane, it appears as a point. This point is its \textbf{position}. A P-line 
	also has a \textbf{direction}. This is not the direction of the line itself 
	(which is always parallel to the Z axis of the Component), but a direction 
	\textit{from the line }in the XY plane. The position and direction are defined in XY coordinates 
	only.
	
	Figure 7-1 shows a two-dimensional view and a three-dimensional view of a 
	P-line on the top of a Section.
	
	P-lines may be used in PARAGON to define the position and orientation of the 
	2D primitives in a Structural Geomset which make up a Profile. They cannot 
	be used to position and orientate the 3D primitives which make up a Joint.
	
	One of the P-lines in a Structural Pointset must be designated as the 
	\textbf{neutral axis p- line}. This is used in DESIGN for positioning and 
	orientating the Component. (The neutral axis is the line where there is no 
	stress in bending, and about which the Component bends.) A P-line is 
	designated as the neutral axis by setting the \textbf{neutral axis reference 
	}attribute (NAREF) of the Structural Pointset to the name of the P-line.
	
	A PLINE has no member elements and has the following attributes:
	
	\begin{itemize}
		\item PKEY - the P-line identifier key
		\item PX,PY - the X, Y coordinates of the P-line
		\item PLAXI - the axis of the P-line, defining its direction
		\item LEVEL - the drawing level range attribute
		\item CLFLA - the centreline drawing flag attribute
		\item TUFLA - the tube drawing flag attribute
		\item DESC - a textual description of the Pline
		\item PURP - the purpose of the Pline
	\end{itemize}
	
	PKEY is a word attribute which identifies the P-line. It is equivalent to 
	the NUMB attribute of a P-point. PLAXI is a direction, equivalent to the 
	PAXI attribute of a P- point.
	
	PKEY must be set as a word. PLAXI must be set as a direction - see Section 
	8.6.3 for details. PX and PY may be set as values or in terms of parameters. 
	The classes of parameter which may be used depend on whether the P-line is 
	used by a Profile or by a Joint - see Section 4.7 for details. Chapter 8 
	gives examples of setting these attributes.
	
	The settings of LEVEL, CLFLA and TUFLA and the use of the 
	\textbf{REPRESENTATION }command affect whether or not the P-line is drawn by 
	PARAGON. LEVEL is a pair of numbers specifying a range and CLFLA and TUFLA 
	are set to TRUE or FALSE (corresponding to `on' or `off' respectively). The 
	way in which LEVEL, TUFLA and CLFLA and the REPRESENTATION settings interact 
	is discussed in Section 6.2. (The settings of LEVEL, CLFLA and TUFLA also 
	affect whether or not the P-line is drawn in DESIGN.)
	
	The primitives in the Geomsets also have LEVEL, CLFLA and TUFLA attributes, 
	which affect whether or not they are drawn in PARAGON and DESIGN.
	
	\textbf{NOTE: }A P-line has its own set of axes, which are used in the 
	design process (not in PARAGON). See the \textit{DESIGN Reference Manual }for details.
	
	\subsection{3D Geomsets (GMSET)}
	\label{subsubsec:mylabel14}
	A GMSET is a grouping of 3D primitive elements which are used to make up 
	Piping Components, Joints and Fittings. It specifies the dimensions, 
	orientation and obstruction geometry of each primitive. The Geomset defines 
	the symbol that is drawn for a particular Component by PARAGON (and DESIGN) 
	and also defines the obstruction geometry of the Component for use when 
	checking for clashes. Each symbol is built up from a combination of the 
	following primitives:
	
	\begin{itemize}
		\item SBOX - rectangular box
		\item BOXI - boxing (used by HVAC and Ducting etc)
		\item SCON - cone
		\item LCYL - cylinder
		\item SCYL - cylinder
		\item SSLC - slope bottomed cylinder
		\item SDIS - disc
		\item SDSH - dish
		\item SLINE - line
		\item LINE - line
		\item LPYR - pyramid
		\item SCTO - circular torus
		\item SRTO - rectangular torus
		\item LSNO - snout
		\item SSPH - sphere
		\item TUBE - tubing
		\item SEXT - user-defined extrusion
		\item SREV - solid of revolution
	\end{itemize}
	GMSET has no attributes other than the standard ones. Each member element of 
	a 3D Geomset has the following attributes in addition to the standard ones:
	
	\begin{itemize}
		\item LEVEL - the drawing level range attribute
		\item CLFLA - the centreline drawing flag attribute
		\item TUFLA - the tube drawing flag attribute
		\item OBST - the obstruction attribute
		\item DESC - a textual description of the Geomset
		\item GTYP - the generic type of the item for which the Geomset is used
		\item PURP - the purpose of the Geomset
	\end{itemize}
	
	The settings of LEVEL, CLFLA and TUFLA affect whether the primitive is drawn 
	or not by PARAGON (or DESIGN), as they do for P-lines. See Section 7.2 for 
	details.
	
	OBST is a number which defines the obstruction level of the primitive for 
	use by DESIGN's clash checking facility:
	
	\begin{itemize}
		\item OBST $=$ 0: No obstruction. The primitive will not clash with anything (used for symbols and negative volumes).
		\item OBST $=$ 1: `Soft' obstruction. Used for insulation, access volumes, penalty volumes, etc.
		\item OBST $=$ 2: `Hard' obstruction. DESIGN's clash checking facility will report hard interference with any item having OBST 1 or 2.
	\end{itemize}
	
	The LEVEL, OBST, CLFLA and TUFLA attributes are common to \textit{all }primitives. Each 
	primitive also has additional attributes depending on its shape; these are 
	described in the next section.
	
	\subsection{3D Geomset Primitives}
	\label{subsubsec:mylabel15}
	The following primitive elements are used by 3D Geomsets. They all have the 
	standard attributes and the common attributes LEVEL, CLFLA, TUFLA and OBST.
	
	\subsubsection{Box (SBOX)}
	\label{para:mylabel12}
	SBOX has particular attributes as follows:
	
	\begin{itemize}
		\item PXLE, PYLE, PZLE - box dimensions in X, Y, Z directions
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.00in,height=4.18in]{Paragon35}}
			\label{fig35}
		\end{figure}
		
		\item PX, PY, PZ - box coordinates
	\end{itemize}
	
	\textbf{Figure 7-2 }SBOX Catalogue Primitive
	
	\subsubsection{Boxing (BOXI)}
	\label{para:boxing}
	Components whose GTYPE attribute is TUBE can use BOXI elements to give, for 
	example, implied tube of rectangular cross-section. BOXI elements can be 
	used for modelling ducting, trunking and cable trays.
	
	BOXI has the following particular attributes:
	
	\begin{itemize}
		\item PXLE - cross-section X-direction length
		\item PZLE - cross-section Z-direction length
		\item PAXI - position and orientation of normal to centre of end face
		\item TVISI - visibility of top face
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.18in,height=4.16in]{Paragon36}}
			\label{fig36}
		\end{figure}
		
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\begin{center}
		\textbf{Figure 7-3 }BOXI Catalogue Primitive
	\end{center}
	
	When implied tube is drawn using BOXI elements, the Y axis of the implied 
	BOXI is set to the PLeave direction of the \textit{preceding }component. The X axis of the BOXI 
	is set to be mutually orthogonal to the PLeave and the Z axis of the 
	preceding component (which usually corresponds to the X axis of the 
	component). The Z axis of the BOXI is then derived from its X and Y axes 
	(and usually corresponds to the Z axis of the component).
	
	A 3D Geomset may contain more than one BOXI element and corresponding 
	P-points may be offset in the X or Z directions.
	
	\textbf{Note for Pipework Designers: }If there is no preceding component 
	(that is, if the implied BOXI forms the Head of a Branch), the Y axis will 
	be set to the Parrive of the \textit{following }component (that is, the first component in the 
	Branch). If there are no components, the BOXI will be set to the orientation 
	of the Zone. (Since Pipe and Branch elements have no coordinate system, this 
	is the lowest level in the design hierarchy from which an orientation can be 
	derived.)
	
	\subsubsection{Cone (SCON)}
	\label{para:mylabel13}
	SCON has particular attributes as follows:
	
	\begin{itemize}
		\item PAXI - direction of axis of cone
		\item PDIS - height of vertex above base
		\item PDIA - diameter of base
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.62in,height=4.63in]{Paragon37}}
		\label{fig37}
	\end{figure}
	
	\textbf{Figure 7-4 }Cone Catalogue Primitive
	
	\subsubsection{Cylinder (LCYL)}
	\label{para:cylinder}
	There are three types of cylinder primitive defined in different ways. LCYL 
	is defined by the distances from the origin to the two end faces. LCYL has 
	particular attributes as follows:
	
	\begin{itemize}
		\item PAXI - direction of axis of cylinder
		\item PDIA - diameter of cylinder
		\item PBDI - distance along axis to centre of bottom surface
		\item PTDI - distance along axis to centre of top surface
		\item TVISI - visibility of top face
		\item BVISI - visibility of bottom face
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.27in,height=5.58in]{Paragon38}}
		\label{fig38}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 7-5 }Cylinder (LCYL) Catalogue Primitive
	\end{center}
	
	\subsubsection{Cylinder (SCYL)}
	\label{para:mylabel14}
	This type of cylinder primitive is defined by the distance to the bottom 
	face from the origin and the height. SCYL has particular attributes as 
	follows:
	
	\begin{itemize}
		\item PAXI - direction of axis of cylinder
		\item PHEI - height of cylinder
		\item PDIA - diameter of cylinder
		\item PDIS - distance along axis to centre of nearest surface
		\item TVISI - visibility of top face
		\item BVISI - visibility of bottom face
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.49in,height=5.14in]{Paragon39}}
		\label{fig39}
	\end{figure}
	
	\textbf{Figure 7-6 }Cylinder (SCYL) Catalogue Primitive
	
	\subsubsection{Slope-Bottomed Cylinder (SSLC)}
	\label{para:slope}
	This is similar to the SLCY available in the Design Data and has its main 
	use in the modelling of mitred bends. SSLC has the following particular 
	attributes:
	
	\begin{itemize}
		\item PAXI - direction of axis of cylinder
		\item PHEI - height of cylinder
		\item PDIA - diameter of cylinder
		\item PXTS - inclination of top face to X-axis
		\item PYTS - inclination of top face to Y-axis
		\item PXBS - inclination of bottom face to X-axis
		\item PYBS - inclination of bottom face to Y-axis
		\item PDIS - distance from origin
		\item TVISI - visibility of top face
		\item BVISI - visibility of bottom face
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.10in,height=0.07in]{Paragon40}}
		\label{fig40}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.14in,height=0.10in]{Paragon41}}
		\label{fig41}
	\end{figure}
	
	\begin{center}
		Y
	\end{center}
	
	PYTS ($+$n)
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.22in,height=0.10in]{Paragon42}}
		\label{fig42}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.10in,height=0.07in]{Paragon43}}
		\label{fig43}
	\end{figure}
	
	\begin{center}
		PAXI
	\end{center}
	
	PHEI
	
	PXBS ($+$n) PXTS (-n)
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.08in,height=0.15in]{Paragon44}}
		\label{fig44}
	\end{figure}
	
	\begin{flushright}
		PDIS
	\end{flushright}
	
	PYBS (-n)
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.00in,height=0.00in]{Paragon45}}
		\label{fig45}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.14in,height=0.21in]{Paragon46}}
		\label{fig46}
	\end{figure}
	
	PDIA
	
	\begin{flushright}
		ORIG
	\end{flushright}
	
	\begin{flushright}
		X
	\end{flushright}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.00in,height=0.00in]{Paragon47}}
		\label{fig47}
	\end{figure}
	
	PDIA
	
	\begin{flushright}
		PAXI
	\end{flushright}
	
	PDIS PHEI
	
	\begin{center}
		\textbf{Figure 7-7 }Slope-Bottomed Cylinder (SSLC) Catalogue Primitive
	\end{center}
	
	\subsubsection{Disc (SDIS)}
	\label{para:mylabel15}
	The Disc primitive is a circular element of zero thickness. SDIS has 
	particular attributes as follows:
	
	\begin{itemize}
		\item PAXI - direction of axis of disc
		\item PDIS - distance along axis to centre of disc
		\item PDIA - diameter of disc
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.20in,height=5.06in]{Paragon48}}
		\label{fig48}
	\end{figure}
	
	\textbf{Figure 7-8 }Disc Catalogue Primitive
	
	\subsubsection{Dish (SDSH)}
	\label{para:mylabel16}
	This is similar to the DISH available in the Design Data. It allows symbolic 
	modelling of control valves and closer modelling of other Components. SDSH 
	has the following particular attributes:
	
	\begin{itemize}
		\item PAXI - direction of axis of dish
		\item PDIS - distance along axis to centre of top surface
		\item PDIA - diameter of dish base
		\item PHEI - maximum height of dished surface above base
		\item PRAD - corner radius
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.55in,height=4.99in]{Paragon49}}
		\label{fig49}
	\end{figure}
	
	If PRAD$=$0 a spherical section dish is drawn, if PRAD\textgreater 0 an 
	ellipsoidal section dish is drawn.
	
	\begin{center}
		\textbf{Figure 7-9 }Dish Catalogue Primitive
	\end{center}
	
	\subsubsection{Line (LINE)}
	\label{para:mylabel17}
	In addition to the three--dimensional primitive elements, 3D Geomsets may 
	contain Line (LINE). A LINE has one particular attribute:
	
	\begin{itemize}
		\item PTS - a set of numbers (up to six) representing P-point numbers of the P- points in the corresponding Pointset, which determine the course of the line.
	\end{itemize}
	
	The values held in PTS are set by the \textbf{SETPoints }command, followed 
	by point specifications in which each p--point identifier is preceded by `P' 
	or `T', e.g. P1 P2 T3 P4. When the P-point is preceded by P it is treated in 
	the same way as a point element (POINT) in the Design Data; when preceded by 
	a T it is treated in the same way as a tangent point element (TANP) in the 
	Design Data. (See \textit{DESIGN Reference Manual }for further details).
	
	\subsubsection{Line (SLINE)}
	\label{para:mylabel18}
	In addition to the three--dimensional primitive elements, an alternative to 
	the LINE element is the SLINE. This has two particular attributes:
	
	\begin{itemize}
		\item PTSPOS - Start position expression
		\item PTEPOS - End position expression
	\end{itemize}
	
	\subsubsection{Pyramid (LPYR)}
	\label{para:pyramid}
	The main use of this element is in the creation of rectangular reducers for 
	ducting etc. LPYR has the particular attributes as follows:
	
	\begin{itemize}
		\item PAAX - direction of axis normal to top face of pyramid (the A axis): this is taken to be in the Z direction
		\item PBAX, PCAX the directions of the two axes perpendicular to the A axis and mutually perpendicular to define the position of the B and C sides
		\item PBTP, PCTP length of top faces in B axis and C axis directions
		\item PBBT, PCBT - length of bottom faces in B axis and C axis directions
		\item PBOF, PCOF top face offsets in B axis and C axis directions
		\item PTDI - distance from origin to centre of top face along A axis
		\item PBDI - distance from origin to centre of bottom face along A axis
		\item TVISI - visibility of top face
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=3.61in,height=4.27in]{Paragon50}}
			\label{fig50}
		\end{figure}
		
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\begin{center}
		\textbf{Figure 7-10 }Pyramid Catalogue Primitive
	\end{center}
	
	\subsubsection{Circular Torus (SCTO)}
	\label{para:circular}
	The circular torus is only part of a torus; it is not permitted to subtend 
	more than 180 degrees. It is circular in cross-section. SCTO has particular 
	attributes as follows:
	
	\begin{itemize}
		\item PAAX, PBAX direction of axes normal to the end faces of the torus
		\item PDIA - diameter of the cross-section of the torus.
		\item TVISI - visibility of top face
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.21in,height=2.61in]{Paragon51}}
			\label{fig51}
		\end{figure}
		
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\textbf{Figure 7-11 }Circular Torus Catalogue Primitive
	
	\subsubsection{Rectangular Torus (SRTO)}
	\label{para:rectangular}
	The rectangular torus is similar to the circular torus except that it is 
	rectangular in cross-section. SRTO has particular attributes as follows:
	
	\begin{itemize}
		\item PAAX, PBAX direction of axes normal to the end faces of the torus
		\item PDIA - width of the cross-section of the torus
		\item PHEI - height of the cross-section of the torus
		\item TVISI - visibility of top face
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.21in,height=2.73in]{Paragon52}}
			\label{fig52}
		\end{figure}
		
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\begin{center}
		\textbf{Figure 7-12 }Rectangular Torus Catalogue Primitive
	\end{center}
	
	\subsubsection{Snout (LSNO)}
	\label{para:snout}
	The Snout primitive is a cylindrical element of varying diameter along its 
	length. It may be eccentric or concentric. LSNO has particular attributes as 
	follows:
	
	\begin{itemize}
		\item PAAX - direction of axis normal to top surface of snout (the A axis)
		\item PBAX - offset direction
		\item PTDI, PBDI - distance along A axis to top, bottom surfaces of snout
		\item PTDM, PBDM diameter of top, bottom surfaces of snout
		\begin{itemize}
			\item POFF - the offset/eccentricity of the snout as measured in the PBAX direction
		\end{itemize}
		\item TVISI - visibility of top face
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.34in,height=4.60in]{Paragon53}}
			\label{fig53}
		\end{figure}
		
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\textbf{Figure 7-13 }Snout Catalogue Primitive
	
	The sizes of the top and bottom surfaces of the snout may be defined in 
	terms of their radii instead of their diameters.
	
	\begin{itemize}
		\item PTRA, PBRA - radius of top, bottom surfaces of snout
	\end{itemize}
	
	\subsubsection{Sphere (SSPH)}
	\label{para:sphere}
	SSPH has particular attributes as follows:
	
	\begin{itemize}
		\item PAXI - direction of axis on which centre of sphere lies
		\item PDIS - distance along axis to centre of sphere
		\item \begin{figure}[htbp]
			\centerline{\includegraphics[width=6.24in,height=4.51in]{Paragon54}}
			\label{fig54}
		\end{figure}
		
		\item PDIA - diameter of sphere
	\end{itemize}
	
	\begin{center}
		\textbf{Figure 7-14 }Sphere Catalogue Primitive
	\end{center}
	
	\subsubsection{Tube (TUBE)}
	\label{para:mylabel19}
	Components whose GTYPE attribute is TUBE can use TUBE Geomset elements to 
	give, for example, implied tube of circular cross-section. TUBE has 
	particular attributes as follows:
	
	\begin{itemize}
		\item PDIAM - tube diameter
		\item TVISI - visibility of top face
		\item BVISI - visibility of bottom face
	\end{itemize}
	
	\subsubsection{User-defined Extrusion (SEXT)}
	\label{para:mylabel20}
	This primitive is generated by extruding a user-defined 2D shape, known as a 
	\textbf{Loop }(\textbf{SLOO}), whose outline is defined by a set of member 
	elements called \textbf{Vertices }(\textbf{SVER}). The lines joining 
	adjacent SVERs form the edges of the SLOO. The extrusion distance is defined 
	by the height of the SEXT to give the final 3D volume.
	
	In addition to the attributes defining its position, each SVER can have a 
	radius which applies a convex or concave fillet to the loop at that point.
	
	SEXT has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY, PZ - coordinates of origin of SLOO
		\item PAAX, - directions of axes of SLOO
	\end{itemize}
	PBAX (these will define coordinate system for SVERs)
	
	\begin{itemize}
		\item PHEI - distance by which 2D SLOO is extruded to form 3D SEXT SLOO has no special attributes.
	\end{itemize}
	SVER has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY - coordinates of vertex
		\item PRAD - fillet radius of loop at vertex position
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.15in,height=0.15in]{Paragon55}}
		\label{fig55}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.15in,height=0.15in]{Paragon56}}
		\label{fig56}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.10in,height=0.08in]{Paragon57}}
		\label{fig57}
	\end{figure}
	
	PBAX of SEXT
	
	(PX,PY)
	
	of SVER
	
	PAAX of SEXT
	
	\begin{flushright}
		PHEI of SEXT
	\end{flushright}
	
	(PX,PY,PZ)
	
	of SEXT
	
	$=$Loop (SLOO)
	
	$=$Vertex (SVER)
	
	\begin{center}
		\textbf{Figure 7-15 }User-defined Extrusion Catalogue Primitive
	\end{center}
	
	\subsubsection{Solid of Revolution (SREV)}
	\label{para:solid}
	This primitive is generated by rotating a user-defined 2D shape, known as a 
	\textbf{Loop }(\textbf{SLOO}), whose outline is defined by a set of member 
	elements called \textbf{Vertices }(\textbf{SVER}), through an angle about an 
	axis. The swept angle must be in the range -360 to $+$360 degrees, 360 
	degrees giving a solid which is axially symmetrical.
	
	In addition to the attributes defining its position, each SVER can have a 
	radius which applies a convex or concave fillet to the loop at that point.
	
	SREV has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY, PZ - coordinates of origin of SLOO
		\item PAAX, - directions of axes of SLOO
	\end{itemize}
	PBAX (these will define coordinate system for SVERs)
	
	\begin{itemize}
		\item PANGLE - angle through which 2D SLOO is rotated to form 3D SREV SLOO has no special attributes.
	\end{itemize}
	SVER has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY - coordinates of vertex
		\item PRAD - fillet radius of loop at vertex position
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.10in,height=0.09in]{Paragon58}}
		\label{fig58}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.10in,height=0.09in]{Paragon59}}
		\label{fig59}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.07in,height=0.11in]{Paragon60}}
		\label{fig60}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=1.85in,height=1.75in]{Paragon61}}
		\label{fig61}
	\end{figure}
	
	Y (PBAX)
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.08in,height=0.08in]{Paragon62}}
		\label{fig62}
	\end{figure}
	
	Origin (PX,PY,PZ)
	
	\begin{flushright}
		SLOO
	\end{flushright}
	
	$=$ SVER
	
	\begin{center}
		PANGLE
	\end{center}
	
	Z
	
	X (PAAX)
	
	\textbf{Figure 7-16 }Solid of Revolution Catalogue Primitive
	
	\subsection{Negative 3D Geomsets (NGMSET) and Negative Primitives}
	\label{subsubsec:negative}
	A NGMSET is a grouping of negative 3D primitive elements which are used to 
	represent holes or end preparations for structural items. It specifies the 
	dimensions, orientation and obstruction geometry of each negative primitive. 
	The attributes of NGMSETs are the same as those of their positive 
	equivalents (see Sections 7.3 and 7.4).
	
	The Negative Geomset defines the symbol that is drawn for a particular 
	Component by PARAGON (and DESIGN) and also defines the obstruction geometry 
	of the Component for use when checking for clashes.
	
	Each symbol is built up from a combination of the following negative 
	primitives:
	
	\begin{itemize}
		\item NSBO - negative rectangular box
		\item NBOX - negative boxing
		\item NSCO - negative cone
		\item NLCY - negative cylinder
		\item NSCY - negative cylinder
		\item NSSL - negative slope bottomed cylinder
		\item NLPY - negative pyramid
		\item NSCT - negative circular torus
		\item NSRT - negative rectangular torus
		\item NLSN - negative snout
		\item NSSP - negative sphere
		\item NTUB - negative tubing
		\item NSEX - negative user-defined extrusion
		\item NSRE - negative solid of revolution
		\item NSRU - negative ruled surface
	\end{itemize}
	Negative Primitives have the same attributes as the corresponding positive 
	primitives, with the addition of the NAPP (\textbf{N}egative 
	\textbf{APP}lies to) attribute, which controls whether the negative 
	primitive is removed from the item itself, or the attached or owning item. 
	The allowed values are:
	
	\textbf{-1 }Default. See following table:
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{62pt}|l|}
				\hline
				Item& 
				Remove from \\
				\hline
				PJOInt& 
				Attached SCTN or GENSEC \\
				\hline
				SJOInt& 
				Attached SCTN or GENSEC \\
				\hline
				SUBJoint& 
				Attached SCTN or GENSEC \\
				\hline
				SCOJoint& 
				Owning PANEl \\
				\hline
				PFITting& 
				Owning PANEl \\
				\hline
				COFItting& 
				Owning PANEl \\
				\hline
				FITTing& 
				Owning SCTN \\
				\hline
				FIXIng& 
				Owning GENSEC \\
				\hline
			\end{tabular}
			\label{tab12}
		\end{center}
	\end{table}
	
	\begin{enumerate}
		\item Negative Primitive will not be removed from anything.
		\item Negative Primitive will be removed from Attached item
		\item Negative Primitive will be removed from Owner
	\end{enumerate}
	\textbf{4 }Negative Primitive will be removed from the item itself
	
	\textbf{7 }Negative Primitive will be removed from all items.
	
	The positive values can be combined so that the hole will be created in more 
	than one item. For example, NAPP$=$6 means that the volume will be removed 
	from the item itself and the item's owner.
	
	The following table shows what Attached and Owner mean for items that can 
	referenced NGMSEs.
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{62pt}|l|l|}
				\hline
				Item& 
				Attached& 
				Owner \\
				\hline
				PJOInt& 
				Attached SCTN or GENSEC& 
				\\
				\hline
				SJOInt& 
				Attached SCTN or GENSEC& 
				Owning SCTN or GENSEC \\
				\hline
				SUBJoint& 
				& 
				Owning PCOJ/SCOJ \\
				\hline
				SCOJoint& 
				& 
				Owning SCTN or GENSEC \\
				\hline
				PFITting& 
				& 
				Owning PANEl \\
				\hline
				COFItting& 
				& 
				Owning PANEl \\
				\hline
				FITTing& 
				& 
				Owning SCTN \\
				\hline
				FIXIng& 
				& 
				Owning GENSEC \\
				\hline
			\end{tabular}
			\label{tab13}
		\end{center}
	\end{table}
	
	For example, if a SUBJoint references a NGMSE which contains an NSBOX with 
	NAPP$=$1, the NSBOX will be removed from the Subjoint's attached Section.
	
	\subsection{Structural Geomsets (GMSSET)}
	\label{subsubsec:mylabel16}
	A GMSSET is a grouping of 2D primitive elements used to make up structural 
	Profiles. It specifies the dimensions, orientation and obstruction geometry 
	of each primitive. The Geomset defines the symbol that is drawn for a 
	particular Component by PARAGON (and DESIGN) and also defines the 
	obstruction geometry of the Component for use when clash checking. Each 
	symbol is built up from a combination of the following three types of 
	primitive:
	
	\begin{itemize}
		\item SREC - rectangle
		\item SANN - annulus
		\item SPRO - user-defined profile
	\end{itemize}
	Like the member elements of a 3D Geomset, each member element of a 
	Structural Geomset has LEVEL, CLFLA, TUFLA and OBST attributes.
	
	\textbf{NOTE: }For correct clash detection, the maximum number of primitives 
	with OBST set to 1 or 2 in any GMSSET is 20; the order of these in the 
	members list is not important. See the \textit{DESIGN Reference Manual }for details of the best way of 
	setting up Component data so as to minimise processing time for clash 
	detection.
	
	The primitives have additional attributes as described in the next section.
	
	\subsection{Structural Geomset Primitives}
	\label{subsubsec:mylabel17}
	The following primitive elements are used by Structural Geomsets. They all 
	have the standard attributes and the common attributes LEVEL, CLFLA, TUFLA 
	and OBST. The additional particular attributes of each element are as 
	described below.
	
	Note that each 2D primitive has effectively \textit{two }types of positional attributes 
	which allow its geometry to be changed progressively as it is extruded in 
	space to create a 3D design element (such as a structural SCTN or GENSEC 
	element). The \textbf{P}... attributes define the geometry at the Start of 
	an extruded section, while the \textbf{D}... attributes define the change in 
	that geometry between the Start and End of the extruded section.
	
	\subsubsection{Structural Rectangle (SREC)}
	\label{para:mylabel21}
	SREC has particular attributes as follows:
	
	\begin{itemize}
		\item PXLE, PYLE - rectangle dimensions in X, Y directions
		\item DXLE, DYLE difference in rectangle dimensions in X, Y directions for
	\end{itemize}
	tapered sections
	
	\begin{itemize}
		\item PX, PY - coordinates of centre of rectangle
		\item DX, DY - offset of coordinates of centre of rectangle between ends of
	\end{itemize}
	section
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.11in]{Paragon63}}
		\label{fig63}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.11in,height=0.09in]{Paragon64}}
		\label{fig64}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.08in,height=0.09in]{Paragon65}}
		\label{fig65}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.07in,height=0.09in]{Paragon66}}
		\label{fig66}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.07in,height=0.09in]{Paragon67}}
		\label{fig67}
	\end{figure}
	
	\begin{itemize}
		\item PLAXI - direction of Y axis of rectangle
	\end{itemize}
	
	\textbf{Figure 7-17 }SREC Catalogue Primitive
	
	\subsubsection{Structural Annulus (SANN)}
	\label{para:mylabel22}
	SANN has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY - coordinates of centre of annulus
		\item DX, DY - offset of coordinates of centre of annulus between ends of
	\end{itemize}
	section
	
	\begin{itemize}
		\item PRAD - external radius
		\item DRAD - change of external radius between ends of section
		\item PWID - width of annulus
		\item DWID - change of width between ends of section
		\item PANG - angle subtended by annulus
		\item PLAXI - start angle
	\end{itemize}
	\textbf{NOTE: }PANG must be in the range -180\textunderscore to 
	$+$180\textunderscore . Positive angles are anticlockwise when the primitive 
	is viewed in the -Z direction.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.22in]{Paragon68}}
		\label{fig68}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.09in]{Paragon69}}
		\label{fig69}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.21in,height=0.09in]{Paragon70}}
		\label{fig70}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.11in,height=0.09in]{Paragon71}}
		\label{fig71}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.11in]{Paragon72}}
		\label{fig72}
	\end{figure}
	
	Y
	
	\begin{center}
		PANGLE
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.19in,height=0.15in]{Paragon73}}
		\label{fig73}
	\end{figure}
	
	PRADIUS
	
	\begin{flushright}
		PLAXIS
	\end{flushright}
	
	\begin{center}
		PWIDTH
	\end{center}
	
	PY
	
	\begin{center}
		PX $^{X}$
	\end{center}
	
	\begin{center}
		\textbf{Figure 7-18 }SANN Catalogue Primitive
	\end{center}
	
	\subsubsection{Structural Profile (SPRO)}
	\label{para:mylabel23}
	This element represents a user-defined 2D shape whose outline is defined by 
	a set of member elements called \textbf{Structural Profile Vertices }(SPVE). 
	The lines joining adjacent SPVEs form the edges of the SPRO.
	
	In addition to the attributes defining its position, each SPVE can have a 
	radius which applies a convex or concave fillet to the profile at that 
	point.
	
	SPRO has particular attributes as follows:
	
	\begin{itemize}
		\item PLAXI - direction of Y axis of profile (this defines coordinate system for SPVEs)
	\end{itemize}
	SPVE has particular attributes as follows:
	
	\begin{itemize}
		\item PX, PY - coordinates of vertex
		\item DX, DY - offset of coordinates between start and end of a tapered section
		\item PRAD - fillet radius of profile at vertex position
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.11in]{Paragon74}}
		\label{fig74}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.11in,height=0.09in]{Paragon75}}
		\label{fig75}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=2.59in,height=2.50in]{Paragon76}}
		\label{fig76}
	\end{figure}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.09in,height=0.08in]{Paragon77}}
		\label{fig77}
	\end{figure}
	
	\begin{itemize}
		\item DRAD - change of fillet radius of profile at vertex position between ends of section
	\end{itemize}
	
	\textbf{Figure 7-19 }SPRO and SPVE Catalogue Primitives
	
	\subsection{Manipulating the Catalogue Database}
	\label{subsec:manipulating}
	This chapter describes how to create and manipulate the member elements of 
	the PDMS Catalogue database.
	
	\subsection{Basic Element Operation Commands}
	\label{subsubsec:basic}
	\textbf{Querying:}
	
	\textbf{QUERY }e.g. \textsf{QUERY ATTRIBUTES}
	
	\textbf{Creation, deletion etc:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{67pt}|l|l|}
				\hline
				\textbf{NEW}& 
				e.g.& 
				\textsf{NEW SECTION} \\
				\hline
				\textbf{DELETE}& 
				e.g.& 
				\textsf{DELETE SREC} \\
				\hline
				\textbf{REORDER}& 
				e.g.& 
				\textsf{REORDER 5 BEFORE 3} \\
				\hline
				\textbf{COPY}& 
				e.g.& 
				\textsf{COPY /VALVES2-1} \\
				\hline
				\textbf{RENAME}& 
				e.g.& 
				\textsf{RENAME /UEANGLE80 /UEANGLE100} \\
				\hline
				\textbf{INCLUDE}& 
				e.g.& 
				\textsf{INCLUDE SCOM 6 OF /FLAN300 BEFORE 2} \\
				\hline
			\end{tabular}
			\label{tab14}
		\end{center}
	\end{table}
	
	\textbf{Implicit element referencing:}
	
	\textbf{OLD END SAME CE OWNER}
	
	\textbf{GOTO }e.g. \textsf{GOTO PTREF}
	
	\textbf{List position changing:}
	
	\textbf{FIRST }(Can be just command word by itself or followed by element
	
	\textbf{LAST }type, for example FIRST LCYL\textbf{)}
	
	\textbf{NEXT}
	
	\textbf{PREVIOUS }\textit{number }list position number, e.g. `5'
	
	\textbf{Standard attribute setting}
	
	\textbf{NAME UNNAME LOCK UNLOCK}
	
	These commands are those which are common to all `constructor' modules of 
	PDMS and some are used in this chapter without further explanation. However, 
	the element types which the above commands operate on relate to the 
	Catalogue database rather than the Design database (so, for example, 
	\textbf{NEXT SITE }is meaningless in PARAGON).
	
	\subsection{Creating Catalogues, Sections and Catalogue Components}
	\label{subsubsec:creating}
	Catalogues and Sections are created using the \textbf{NEW }command. You 
	would normally also specify names by which you can recognise and refer to 
	the elements created. For example:
	
	\textsf{NEW CATA /ANSI-CATALOGUE}
	
	will create a Catalogue with the name /ANSI-CATALOGUE in the Catalogue 
	database.
	
	\textsf{NEW SECT /FLANGES NEW STSEC /PROFILES}
	
	will create a Piping Section with the name /FLANGES and a Structural Section 
	with the name /PROFILES. Similarly,
	
	\textsf{NEW CATEG /ANSI-B16.5-CLASS-300-BLIND-FLANGES NEW STCAT 
		/UNIVERSAL-BEAM}
	
	will create a Piping Category and a Structural Category with the names 
	given.
	
	A Catalogue Component is represented by one of the Component elements SCOM, 
	SPRF, SJOI, SFIT (see Section 4.8).
	
	\textsf{NEW SCOM}
	
	will create a Piping Component with unspecified component parameters, the 
	values of which may be set later.
	
	If the Component is to be named, this can be done at the same time; for 
	example,
	
	\textsf{NEW SFIT /EKAA2VEE}
	
	The attributes of the Component (see Section 4.8) are set simply by 
	following the attribute with the word, name or value(s) to be assigned to 
	it. For example:
	
	\textsf{NEW SCOM GTYPE ELBO PTREF /PSE1 GMREF /GSE1}
	
	\textsf{PARAM 20 19.1 12.7 37.1 BWD}
	
	The above commands create a Piping Component, of generic type ELBO, which is 
	defined by 3D Pointset /PSE1 and 3D Geomset /GSE1, and which has the five 
	component parameters shown. The Pointset and Geomset which are referred to 
	by name must already exist; they would have been created by the commands
	
	\textsf{NEW PTSET /PSE1 NEW GMSET /GSE1}
	
	All five component parameters have been given values using a single command 
	line, but they can be given values individually by using commands such as
	
	\textsf{PARAM[1] 20}
	
	\textsf{PARAM\textbraceleft 2] 19}
	
	...
	
	etc.
	
	\textbf{NOTE: }You can only use the \textbf{PARAM[}\textit{number}] syntax to change the 
	value of a parameter which has already been set.
	
	This facility allows component parameter definitions to be `edited'. 
	(\textbf{Caution: }If you delete a COMP which is referred to by a SPCO - via 
	the CATREF attribute of a design component - this reference will be lost.). 
	The use of component parameters and the other classes of parameter is 
	discussed and illustrated in the next section.
	
	\textbf{NOTE: }If you give a \textbf{PARAM }command with, say, four values 
	as a single command line, PARAGON sets the values of the first four 
	component parameters and \textit{deletes }all the rest.
	
	You may define default values which PARAGON will use if you are working with 
	a Component whose component parameters have not been set up. See Section 4.7 
	for details.
	
	The attributes of a Component may be queried by a
	
	\textbf{QUERY ATTRIBUTES}
	
	command, or may be queried individually by name. Component parameters can be 
	queried as a set by using the command
	
	\textsf{QUERY PARAMETERS}
	
	or singly by using commands such as
	
	\textsf{QUERY PARAMETER[1] QUERY PARAMETER[2}]
	
	etc.
	
	\subsection{Using Parameters}
	\label{subsubsec:using}
	\subsubsection{Introduction}
	\label{para:introduction}
	Piping Components, Profiles and Fittings each use one type of Pointset and 
	one type of Geomset. Joints use both types of Pointset and one type of 
	Geomset. The attributes of Pointsets and Geomsets may be defined in terms of 
	parameters, set either explicitly or as real expressions (which may 
	themselves incorporate the current settings of other parameters). (The 
	classes of parameter which may be used depend on the class of Component - 
	see Section 4.7 for details.)
	
	For example, the bore of a P-point could be defined by entering
	
	\textsf{PBORE (PARAM[1])}
	
	This means that the value assigned to the bore of the P-point is the value 
	of the first component parameter.
	
	The Y dimension of a box in a 3D Geomset used by a Joint could be defined as 
	the expression
	
	\textsf{PYLEN (APARAM[2] }$+$\textsf{ 3)}
	
	This means that the Y dimension of the box is to be given a value in the 
	design process, taken from the Section to which the Joint is attached. The 
	value of the Y dimension of the box is the value of the second component 
	parameter of the attached Profile plus 3 mm.
	
	The use of parameters makes it possible to use the same Pointsets and 
	Geomsets for large numbers of catalogue items. For example, there may be 
	families of tees, valves, \textsf{I}- beam profiles etc., each family 
	containing items which are geometrically similar. In this way, the Catalogue 
	size and the effort needed to prepare input data are minimised.
	
	Examples of the parameterisation of typical Components are given later in 
	this chapter.
	
	The values assigned to parameters, the uses to which they are put, and the 
	number of parameters used, are arbitrary, depending only on the skill and 
	experience of the user, \textit{except }in the special case of a Piping Component which 
	represents implied tubing (GTYPE attribute set to TUBE) \textit{and }which has no 
	Geomset. In this case, component parameter 2 \textit{must }be the outside diameter. If the 
	tube is to be insulated, insulation parameter 1 \textit{must }be twice the thickness of 
	the insulation.
	
	\textbf{Note on the use of Insulation Parameters}: Insulation parameters may 
	be used in two ways. They may be used in an additive manner to increase the 
	diameter or length of a primitive or, if there is a significant change in 
	the geometry from the uninsulated to the insulated form, they may be used to 
	define a new primitive. Where there is no insulation, the insulation 
	parameters will be zero, yielding a primitive of zero diameter (but probably 
	non-zero length).
	
	\subsubsection{Expressions Using Parameters}
	\label{para:expressions}
	Any expression which includes parameters and which evaluates to a real 
	result may be built into definitions of Pointsets and Geomsets. For example:
	
	\textsf{PDIA (4.5 * PARA[2]) PDIS (-PARA[2])}
	
	\textsf{PBOR (PARA[7] }$+$ \textsf{IPARA[1]) PHEI (PARA[2] }$+$ \textsf{50)}
	
	\textsf{PDIS (APARA[2] - PARA[7]) PDIA (-(PARA[1] - PARA[5])) PX (2 * 
		OPARA[3])}
	
	\textsf{PTDIS (PARA[2] * DESP[5]) PHEI (PARA[4] / ODESP[1])}
	
	\textsf{PZ (5 * (ADESP[3] * PARA[9]) PDIS (3.1 * (PARA[1] }$+$\textsf{ 
		HEIG)) PHEI (PARA[1] * TAN (ANGL / 2))}
	
	(For the full range of expression syntax available, see the \textit{Plant Design Software Customisation Guide}.)
	
	\subsection{Examples of Parameterisation}
	\label{subsubsec:examples}
	\begin{center}
		\textbf{Example 1 A Slip-On Flange}
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.15in,height=3.99in]{Paragon78}}
		\label{fig78}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 8-1 }Example of Parameterisation for a Slip-On Flange
	\end{center}
	
	A slip-on flange can be parameterised using five component parameters, as 
	shown in Figure 8-1.
	
	\begin{itemize}
		\item PARAM 1 - PBORE
		\item PARAM 2 - Outside Diameter
		\item PARAM 3 - Thickness
		\item PARAM 4 - Connection Type at P1
		\item PARAM 5 - Connection Type at P2
	\end{itemize}
	
	\begin{center}
		\textbf{Example 2 A Reducing Tee}
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.15in,height=3.99in]{Paragon79}}
		\label{fig79}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 8-2 }Example of Parameterisation for a Reducing Tee
	\end{center}
	
	A reducing tee might be parameterised using 12 component parameters, as 
	shown in Figure 8-2.
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{63pt}|l|l|}
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				1& 
				Nominal bore of main run (PBOR1) \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				2& 
				Outside diameter of main run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				3& 
				Nominal bore of branch (PBOR3) \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				4& 
				Outside diameter of branch \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				5& 
				Half overall length of main run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				6& 
				Standout length of branch run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				7& 
				Connection type of main run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				8& 
				Connection type of branch run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				9& 
				Flange diameter of main run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				10& 
				Flange thickness of main run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				11& 
				Flange diameter of branch run \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				12& 
				Flange thickness of branch run \\
				\hline
			\end{tabular}
			\label{tab15}
		\end{center}
	\end{table}
	
	Other families of tees could be defined as follows:
	
	\begin{itemize}
		\item Equal and reducing welded tees using parameters 1-8
		\item Equal and reducing flanged tees using all the parameters
	\end{itemize}
	
	\begin{center}
		\textbf{Example 3 A Universal Beam Profile}
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.16in,height=4.00in]{Paragon80}}
		\label{fig80}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 8-3 }Example of Parameterisation for a Universal Beam Profile
	\end{center}
	
	A Universal Beam Profile might be parameterised using four component 
	parameters, as shown in Figure 8-3.
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{65pt}|l|l|}
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				1& 
				Overall height of Profile \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				2& 
				Flange width \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				3& 
				Web thickness \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				4& 
				Flange thickness \\
				\hline
			\end{tabular}
			\label{tab16}
		\end{center}
	\end{table}
	
	\begin{center}
		\textbf{Example 4 An Angle Joint}
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.16in,height=3.99in]{Paragon81}}
		\label{fig81}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 8-4 }Example of Parameterisation for an Angle Joint
	\end{center}
	
	An Angle Joint might be parameterised using three component parameters and 
	two attached parameters, as shown in Figure 8-4.
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{63pt}|l|l|}
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				1& 
				Overall height of angle leg \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				2& 
				Overall length of angle foot \\
				\hline
				\begin{itemize}
					\item PARAM
				\end{itemize}
				& 
				3& 
				Thickness of leg and foot \\
				\hline
				\begin{itemize}
					\item APARA
				\end{itemize}
				& 
				1& 
				Height of profile of attached Section \\
				\hline
				\begin{itemize}
					\item APARA
				\end{itemize}
				& 
				2& 
				Width of flange of attached Section \\
				\hline
			\end{tabular}
			\label{tab17}
		\end{center}
	\end{table}
	
	\subsection{Constructing 3D Pointsets}
	\label{subsubsec:constructing}
	A 3D Pointset defines the connection information of a Piping Component, 
	Joint or Fitting as explained in Section 7.1. For the three types of P-point 
	elements which may be contained in a 3D Pointset, you must define the 
	following attributes:
	
	\textbf{PTAXI}
	
	\begin{itemize}
		\item A P-point number (NUMB)
		\item An axis direction (PAXI) (parallel to X, Y, Z or in the XY, YZ or ZX plane)
		\item A distance along the specified axis (PDIS)
	\end{itemize}
	
	If the Pointset is used by a Piping Component, you may optionally define the 
	attributes:
	
	\begin{itemize}
		\item Connection type (PCON)
		\item Bore (PBOR)
		\item P-point symbol key (PSKEY) (see Section 8.5.8)
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.16in,height=3.99in]{Paragon82}}
		\label{fig82}
	\end{figure}
	
	PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
	
	\textbf{Figure 8-5 }Example of three Axial P-Points
	
	\textbf{PTCAR}
	
	\begin{itemize}
		\item A P-point number (NUMB)
		\item An axis direction (PTCDIR) (in any plane)
		\item An explicit position (PX, PY, PZ) (explicit coordinates)
	\end{itemize}
	
	If the Pointset is used by a Piping Component, you may optionally define the 
	attributes:
	
	\begin{itemize}
		\item Connection type (PCON)
		\item Bore (PBOR)
		\item P-point symbol key (PSKEY) (see Section 8.5.8)
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.16in,height=4.00in]{Paragon83}}
		\label{fig83}
	\end{figure}
	
	PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
	
	\begin{center}
		\textbf{Figure 8-6 }Example of two Cartesian P-Points
	\end{center}
	
	\textbf{PTMIX}
	
	\begin{itemize}
		\item A P-point number (NUMB)
		\item An axis direction (PAXI) (parallel to X, Y, Z or in the XY, YZ or ZX plane)
		\item An explicit position (PX, PY, PZ) (explicit coordinates)
	\end{itemize}
	
	If the Pointset is used by a Piping Component, you may optionally define the 
	attributes:
	
	\begin{itemize}
		\item Connection type (PCON)
		\item Bore (PBOR)
		\item P-point symbol key (PSKEY) (see Section 8.5.8)
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.15in,height=4.00in]{Paragon84}}
		\label{fig84}
	\end{figure}
	
	PCON and PBOR are meaningless if the Pointset is used by a Joint or Fitting.
	
	\textbf{Figure 8-7 }Example of two Mixed P-Points
	
	\begin{enumerate}
		\item \textbf{Example of Defining a 3D Pointset}
	\end{enumerate}
	A suitable 3D Pointset for the reducing tee shown in Figure 8-2 would be 
	created as follows:
	
	\textsf{NEW PTSET /RTPTSE }Create new 3D Pointset
	
	\textsf{NEW PTAX }Create axial P-point element
	
	\textsf{NUMBER 1 }P1
	
	\textsf{PAXI -Y }Direction of P1 along negative Y axis
	
	\textsf{PDIS (PARA[5]) }Distance along axis from P0 $=$ half overall length
	
	\textsf{PCON (PARA[7]) }Connection type at P1 \textsf{PBOR (PARA[1]) 
	}Nominal bore at P1 \textsf{NEW PTAX}
	
	\textsf{NUM 2 PAXI Y PDIS (PARA[5]) PCON (PARA[7]) PBOR (PARA[1]) NEW PTAX}
	
	\textsf{NUM 3 PAXI X PDIS (PARA[6]) PCON (PARA[8]) PBOR (PARA[3])}
	
	Notice how all the P-point attributes may be defined on one line. The last 
	P-point (P3) could alternatively be defined as a Cartesian P-point:
	
	\textsf{NEW PTCAR}
	
	\textsf{NUM 3 PCON (PARA[8]) PBOR (PARA[3]) PX (PARA[6]) PY 0 PZ 0}
	
	\textsf{PTCDIR X}
	
	Further examples of the construction of typical 3D Pointsets are given in 
	Appendix C. Reference information concerning the setting up of the P-point 
	attributes is given in the following subsections.
	
	\subsubsection{Defining an Axis}
	\label{para:defining}
	The PAXI attribute of a P-point can be defined in one of two ways:
	
	\begin{itemize}
		\item by a direction letter, e.g. PAXI Z
		\item by an angle in the XY plane (see below). You can specify the angle as
		\begin{itemize}
			\item a number
		\end{itemize}
		\item DDANGLE
		\begin{itemize}
			\item a parameter
			\item TWICE a parameter
		\end{itemize}
	\end{itemize}
	
	The classes of parameter which you can use depend on the class of the 
	Component which uses the P-point - see Section 4.7 for details.
	
	If you do not define the axis, PAXI Y is assumed.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.17in,height=13.32in]{Paragon85}}
		\label{fig85}
	\end{figure}
	
	\textbf{Figure 8-8 }P-point Axis Definition
	
	\subsubsection{Defining a Distance}
	\label{para:mylabel24}
	Distance in a PTAXI element is defined by the \textbf{PDISTANCE }keyword 
	(minimum abbreviation \textbf{PDIS}) followed by a value or a parameter 
	function. For example:
	
	\textsf{PDIS 100 }sets P-point position to 100 units along defined axis
	
	\textsf{PDIS (PARAM[1]) }sets P-point position to (value of first component
	
	parameter) units along defined axis If you do not define the distance, a 
	value of zero is assumed.
	
	For the reducing tee shown in Figure 8-2, the position of P-point 3 could be 
	defined by the commands:
	
	\textsf{PAXI X}
	
	\textsf{PDIS (PARAM[2])}
	
	since PARAM 2 is the dimension called `height'.
	
	\subsubsection{Defining an Explicit Position}
	\label{para:mylabel25}
	Position in a PTCAR element and a PTMIX element is defined by the 
	\textbf{PX}, \textbf{PY }and \textbf{PZ}
	
	keywords, each followed by a value or a parameter function. For example:
	
	\textsf{PX 100 }sets P-point X coordinate to 100
	
	\textsf{PY (0.5 * APARA[3]) }sets Y coordinate to (0.5 times value of third 
	attached parameter) units
	
	\textsf{PZ (PARA[2] * SIN (ANGLE / 2)) }sets Z coordinate to (second
	
	component parameter times sine of half design angle) units
	
	If you do not define a coordinate, a value of zero is assumed.
	
	\subsubsection{Defining a Direction}
	\label{para:mylabel26}
	Direction in a PTCAR element is defined by the \textbf{PTCDIRECTION }keyword 
	(minimum abbreviation \textbf{PTCDIR}), followed by the direction specified 
	in terms of the X, Y, Z axes and rotations towards those axes. For example:
	
	\textsf{PTCDIR X45Y }direction is along the X axis, rotated 45 degrees 
	towards the Y axis
	
	\textsf{PTCDIR X(ANGL / 2)Y45U }includes an expression for the Y
	
	component
	
	For other examples, see Figure 8-6. Note that any one, any two, or all three 
	of X, Y, Z may be present in the \textbf{PTCDIR }command line, in any order. 
	The rotation value may be positive, negative or absent altogether (i.e. 
	zero). If you do not define the direction, DIR Y is assumed.
	
	\subsubsection{Defining Connection, Bore and Number}
	\label{para:mylabel27}
	These three attributes are common to all three types of P-point elements, 
	and are set by the \textbf{PBORE}, \textbf{PCONNECTION }and \textbf{NUMBER 
	}(minimum abbreviations \textbf{PBOR}, \textbf{PCON}, \textbf{NUM}) commands 
	respectively. PBOR and PCON may be set as parameter functions as well as 
	words. Examples:
	
	\textsf{PBORE (0.5 * PARAM[2]) PCONN BWD}
	
	\textsf{PCONN (PARAM[7]) NUMBER 3}
	
	If you do not define the bore or the P-point number, a value of zero is 
	assumed.
	
	\subsubsection{Controlling the Appearance}
	\label{para:controlling}
	How a P-point is drawn depends on the REPRESENTATION settings. This is 
	discussed in Section 6.2.
	
	\subsubsection{Specifying Pipe End Conditions for use by ISODRAFT}
	\label{para:specifying}
	The symbol used by ISODRAFT to represent a particular piping component on an 
	isometric drawing is determined by the \textbf{symbol key }(SKEY attribute 
	setting) for that component. (See the \textit{ISODRAFT Reference Manual }for a full explanation of this 
	concept.)
	
	By default, each SKEY has associated with it a standard end condition 
	(showing the pipe connection type) which applies to each of the component's 
	connection points. The end condition for any individual connection point may 
	be modified, if required, by setting the PSKEY attribute of the 
	corresponding P-point to a PDMS word chosen from the following:
	
	\textbf{BW }Butt Weld
	
	\textbf{CP }Compression
	
	\textbf{FL }Flange
	
	\textbf{SC }Screwed
	
	\textbf{SW }Socket Weld
	
	\textbf{PL }Plain
	
	The effect of setting PSKEY to one of these words for a P-point of type 
	PTAXI, PTCAR or PTMIX is that ISODRAFT will then add the symbolic 
	representation of the specified end condition to the symbol derived from the 
	corresponding SKEY when it plots an isometric drawing showing the component. 
	The default setting for PSKEY is always \textbf{NULL}, which means that 
	ISODRAFT plots only the standard end conditions for the symbol.
	
	Note that the effect is \textit{additive}, so that ISODRAFT superimposes any user-specified 
	end condition (derived from a non-Null PSKEY setting) on top of any end 
	condition which forms part of the standard symbol associated with the SKEY. 
	The use of the PSKEY facility is, therefore, applicable mainly to components 
	which do not have other end conditions already defined, particularly those 
	associated with user-defined symbols (as detailed in the \textit{ISODRAFT Reference Manual}).
	
	\subsection{Constructing Structural Pointsets}
	\label{subsubsec:mylabel18}
	A Structural Pointset defines the connection information of a Profile or 
	Joint as explained in Section 7.2. A Structural Pointset has a 
	\textbf{neutral axis reference }attribute in addition to the standard 
	attributes, and contains P-lines.
	
	\subsubsection{Example of Defining a Structural Pointset}
	\label{para:example}
	A suitable Structural Pointset for the Profile shown in Figure 8-3 would be 
	created as follows:
	
	\textsf{NEW PTSSET /UBPTSE }Create new Structural Pointset
	
	\textsf{NEW PLIN /UB-TOS }Create P-line element for top of steel
	
	\textsf{PKEY TOS }Define key
	
	\textsf{PLAXI Y }Direction of P-line along positive Y axis
	
	\textsf{PY (0.5 * PARA[1]) }Distance in Y direction from component origin 
	$=$
	
	half overall height. (There is no need to set PX, because it is zero.)
	
	\textsf{CLFLA TRUE }Display P-line in centreline representation
	
	\textsf{TUFLA FALSE }but not in tube representation
	
	\textsf{NEW PLIN /UB-BOS }Create new P-line element for bottom of steel
	
	\textsf{PKEY BOS PLAXI -Y PY (-0.5 * PARA[1]) CLFLA TRUE TUFLA FALSE}
	
	\textsf{NEW PLIN /UB-NA }- Create new P-line element for neutral axis
	
	\textsf{PKEY NAXI PLAXI Y CLFLA TRUE TUFLA FALSE}
	
	\textsf{END }Make the Structural Pointset the current element
	
	\textsf{NAREF /UB-NA }Define neutral axis reference
	
	Notice how all the P-line attributes may be defined on one line. Reference 
	information concerning the setting up of the P-line attributes is given in 
	Sections 8.6.3 to 8.6.6.
	
	\subsubsection{The Neutral Axis Reference}
	\label{para:mylabel28}
	The neutral axis reference identifies a P-line in the Structural Pointset. 
	It is set by the \textbf{NAREF }command. The attribute is usually set to the 
	name of the P-line, but may be set to the P-line's number in the member list 
	of the Pointset. For example:
	
	\textsf{NAREF /UB-NA }Sets neutral axis reference to the P-line called
	
	/UB-NA
	
	\textsf{NAREF 3 }Sets neutral axis reference to the third P-line of the 
	Structural Pointset
	
	If you do not set NAREF, DESIGN will make an assumption about where the 
	neutral axis is. You are strongly recommended to set the neutral axis 
	reference in the Catalogue.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.16in,height=3.94in]{Paragon86}}
		\label{fig86}
	\end{figure}
	
	DESIGN will use as the neutral axis the first P-line in the Structural 
	Pointset which has a PKEY value of NA, if any. Failing that, it will choose 
	the first P-line with a PKEY value of NAXI, and failing \textit{that}, it will choose the 
	first P-line with a PKEY value of ZAXI. If there are no P-lines with a PKEY 
	value of NA or NAXI or ZAXI, DESIGN will assume that the neutral axis of the 
	Component lies at the component origin and has a direction along the 
	positive Y axis.
	
	\textbf{Figure 8-9 }P-line Axis Definition
	
	\subsubsection{Defining an Axis}
	\label{para:mylabel29}
	The PLAXI attribute of a P-line can be defined in one of two ways:
	
	\begin{itemize}
		\item by a direction letter, e.g. PLAXI Y
		\begin{itemize}
			\item by an angle in the XY plane (see below). You can specify the angle as
			\begin{itemize}
				\item a number
			\end{itemize}
			\item DDANGLE
			\begin{itemize}
				\item a parameter
				\item TWICE a parameter
			\end{itemize}
		\end{itemize}
	\end{itemize}
	
	The classes of parameter which you can use depend on the class of the 
	Component which uses the P point - see Section 4.7 for details.
	
	If you do not define the axis, PLAXI Y is assumed.
	
	\subsubsection{Defining a Position}
	\label{para:mylabel30}
	Position in a P-line element is defined by the \textbf{PX }and \textbf{PY 
	}keywords, each followed by a value or a parameter function. For example:
	
	\textsf{PX 50 }sets P-line X coordinate to 50
	
	\textsf{PY (0.5 * DESPAR[2]) }sets P-line Y coordinate to 0.5 * (value of
	
	second design parameter) units If you do not define a coordinate, a value of 
	zero is assumed.
	
	\subsubsection{Defining a Key}
	\label{para:mylabel31}
	A P-line is identified by its key in the same way as a P-point is identified 
	by its number. The key is defined by the \textbf{PKEY }keyword followed by a 
	word. For example:
	
	\textsf{PKEY TOS }sets P-line key to TOS PKEY may be set to any desired word 
	value. Typical values are:
	
	\textsf{TOS }Top of steel, for a P-line at the top of the Profile
	
	\textsf{BOS }Bottom of steel, for a P-line at the bottom of the Profile
	
	\textsf{NA, NAXI }\textit{or }\textsf{ZAXI }Neutral axis P-line
	
	\subsubsection{Controlling the Appearance}
	\label{para:mylabel32}
	Whether a P-line is drawn or not depends on the settings of its LEVEL, TUFLA 
	and CLFLA attributes, and the REPRESENTATION settings. How a P-line is drawn 
	also depends on the REPRESENTATION settings. See Section 6.2 for details.
	
	\subsection{Constructing 3D Geomsets}
	\label{subsubsec:mylabel19}
	A 3D Geomset is a grouping of the primitive elements which make up a Piping 
	Component, Joint or Fitting. It specifies the dimensions, orientation and 
	obstruction geometry of each primitive. The Geomset defines what is drawn 
	for a particular Component by PARAGON (and other PDMS modules), and also 
	defines the obstruction geometry of the Component for use when clash 
	checking. Each Component is built up from a combination of three-dimensional 
	primitives, as listed in Section 7.3.
	
	Creating a Geomset consists of creating the relevant member primitives and 
	setting the attributes for each primitive. For each primitive the OBST 
	attribute must be set, whilst for a primitive that is required to be drawn 
	the LEVEL, TUFLA and CLFLA attributes must also be set. (See Chapter 6 and 
	the \textit{DESIGN Reference Manual }for details of these attributes.) 3D Geomset elements and their 
	attributes are listed in Section 7.4.
	
	\textbf{NOTE: }Only the first 20 primitives in a Geomset with OBST values of 
	1 or 2 are considered by DESIGN's clash checking facility.
	
	By using the TUFLA and CLFLA flags, you can create two different drawings of 
	a Component, a double-line representation (\textbf{tube}) and a single-line 
	`stick' representation (\textbf{centreline}).
	
	To define the tube representation for the tee shown in Figure 8-2 (with 
	clash geometry) the commands shown below could be used. (The P-points in the 
	following examples relate to the Pointset defined in section 8.5.1.)
	
	\textsf{NEW GMSET /RTGMSE }Create new 3D Geomset
	
	\textsf{NEW SCYL }Create cylinder primitive
	
	\textsf{PAXI -Y }Direction of axis on which SCYL origin lies
	
	\textsf{PDIS (PARA[5]) }Distance of SCYL origin from tee origin $=$ half 
	overall length
	
	\textsf{PDIA (PARA[2]) }Outside diameter of main run
	
	\textsf{PHEI (-2 * PARA[5]) }Height of SCYL
	
	\textsf{OBST 2 }Set obstruction value as `hard'
	
	\textsf{TUFL TRUE CLFL FALSE }Set drawing flags
	
	\textsf{NEW SCYL PAXI X PDIS 0}
	
	\textsf{PHEI (PARA[6])}
	
	\textsf{PDIA (PARA[4]) OBST 2}
	
	\textsf{TUFL TRUE CLFL FALSE}
	
	To define the centreline representation for the tee (with welded joints), 
	the following commands could be used. Figure 8-10 shows the symbol produced. 
	The illustration is drawn with \textsf{REPRESENTATION PPOINTS ON LENGTH 0 
		NUMBERS ON. The }P-points
	
	are thus displayed as dots, but they cannot be seen because they lie on the 
	displayed LINEs.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.21in,height=13.31in]{Paragon87}}
		\label{fig87}
	\end{figure}
	
	\begin{center}
		\textbf{Figure 8-10 }Centreline Representation of a Reducing Tee
	\end{center}
	
	\textsf{NEW SSPH }Create sphere primitive (to represent weld)
	
	\textsf{PAXI -Y }Direction of axis on which sphere origin lies
	
	\textsf{PDIS (PARA[5]) }Distance of sphere origin from tee origin $=$ half
	
	overall length
	
	\textsf{PDIA (0.1 * PARA[1]) }Sphere diameter relative to bore size
	
	\textsf{OBST }0 Clash checking to ignore item
	
	\textsf{TUFLA FALSE CLFL TRUE }Set drawing flags
	
	\textsf{NEW SSPH}
	
	\textsf{PAXI P2 }Set axis direction and origin in terms of P-point 2
	
	\textsf{PDIS }0 \textsf{PAXI P2 PDIS 0 }is equivalent to
	
	\textsf{PAXI Y PDIS (PARA[5]))}
	
	\textsf{PDIA (0.1 * PARA[1]) OBST 0}
	
	\textsf{CLFL TRUE NEW SSPH}
	
	\textsf{PAXI P3 PDIS 0 PDIA (0.1 * PARA[3]) OBST 0 CLFL TRUE}
	
	\textsf{NEW LINE P3 P0 }Define line elements
	
	\textsf{OBST 0 CLFL TRUE DIAM 1 NEW LINE P1 P2}
	
	\textsf{OBST 0 CLFL TRUE DIAM 1}
	
	Note how a P-point has been used to define an axis direction and origin for 
	a primitive - see the Reference Section at the end of this chapter for 
	details.
	
	To put the flanges on the tee the first two representations (as given above) 
	would remain the same but the centreline representation would not need the 
	SSPH elements (which represent the welds). The latter are replaced by using 
	the following commands to represent the flanged connections:
	
	\textsf{NEW SCYL PAXI P1 PHEI (-PARA[10]) PDIA (PARA[9]) PDIS 0 OBST 2 CLFL 
		TRUE TUFL TRUE}
	
	\textsf{NEW SCYL COPY PREV PAXI P2}
	
	\textsf{NEW LCYL PAXI P3 PTDI 0 PBDI (-PAR[12]) PDIA (PAR[11]) OBST 2 CLFL 
		TRUE TUFL TRUE}
	
	\subsection{Constructing Structural Geomsets}
	\label{subsubsec:mylabel20}
	A Structural Geomset is a grouping of the 2D primitive elements which make 
	up a Profile. Like the 3D Geomset, it specifies the dimensions, orientation 
	and obstruction geometry of each primitive. It also defines the symbol that 
	is drawn for a particular Component and the obstruction geometry of the 
	Component. The Profile is built up from a combination of Structural 
	Rectangles (SREC) and Structural Annuli (SANN), as described in Section 7.6. 
	Structural Geomset elements and their attributes are listed in Section 7.7.
	
	To define the tube representation for the Profile shown in Figure 8-3, the 
	commands shown below could be used. A simplified clash geometry for the 
	Profile is specified by defining a bounding box for the Profile with `hard' 
	obstruction and giving the primitives of the Profile itself 'no 
	obstruction'. The P-lines used are those defined in Section 8.6.1.
	
	\textsf{NEW GMSSET /UBGMSS }Create new 2D Geomset
	
	\textsf{NEW SRECT }Create rectangle primitive for web
	
	\textsf{PXLE (PARA[1]) }Web thickness
	
	\textsf{PYLE (PARA[1] - 2 * PARA[4]) }Web length
	
	(PX and PY are zero, so there is no need to set them)
	
	\textsf{PLAXI Y }Direction of axis of rectangle
	
	\textsf{TUFL TRUE CLFL FALSE }Set drawing flags
	
	\textsf{OBST }Set obstruction value as `none'
	
	\textsf{NEW SRECT }Create rectangle primitive for upper flange
	
	\textsf{PXLE (PARA[2]) PYLE (PARA[4]) }Flange length and thickness 
	\textsf{PY (0.5 * (PARA[1] }-\textsf{ PARA[4])) }Position of rectangle 
	origin \textsf{PLAXI Y }Direction of axis of rectangle
	
	\textsf{TUFL TRUE CLFL FALSE }Set drawing flags
	
	\textsf{OBST }Set obstruction value as `none'
	
	\textsf{NEW SRECT }Create rectangle primitive for lower flange
	
	\textsf{PXLE (PARA[2]) PYLE (PARA[4])}
	
	\textsf{PY (-0.5 * (PARA[1] - PARA[4])) PLAXI Y}
	
	\textsf{TUFL TRUE CLFL FALSE OBST 0}
	
	\textsf{NEW SRECT }Create rectangle which bounds the Profile
	
	\textsf{PXLE (PARA[2]) PYLE (PARA[1])}
	
	\textsf{PLAXI Y}
	
	\textsf{TUFL FALSE CLFL FALSE }Set both drawing flags `off'
	
	\textsf{OBST 2 }Set obstruction value as `hard'
	
	A P-line may be used to define an axis direction and position for a 
	primitive. The example below shows how the upper flange could be positioned 
	and orientated using a P- line. See the Reference Section at the end of this 
	chapter for details.
	
	\textsf{PLAXI TOS }Set axis direction and origin in terms of P-line TOS
	
	\textsf{PY (-0.5 * PARA[4]) }Position of rectangle origin relative to 
	position of P-line
	
	\subsection{Reference Section}
	\label{subsubsec:mylabel21}
	\subsubsection{Parameter-Controlled Attributes}
	\label{para:parameter}
	The following attributes of P-points, P-lines and Geomset primitives may be 
	set equal to parameters or functions of parameters (as well as to constant 
	values):
	
	\textsf{PDIStance PBDIstance PTDIstance PBBT PBTP PCBT PCTP}
	
	\textsf{PDIAmeter PBDMeter PTDMeter}
	
	\textsf{PRADius PBRAdius PTRAdius PWIDth PANGle POFFset PBOFfset PCOFfset}
	
	\textsf{PX PXLEngth PY PYLEngth PZ PZLEngth PBORe PCONnect PHEIght}
	
	\textsf{PXTShear PYTShear PXBShear PYBShear}
	
	\subsubsection{Axial Attributes}
	\label{para:mylabel33}
	Axial attributes of both 3D and 2D primitives define a position and a 
	direction. An axial attribute of a 3D primitive may be specified as a 
	direction in one, two or three dimensions or as a P-point. Similarly, the 
	axial attribute of a 2D primitive may be specified as a direction in one or 
	two dimensions or as a P-line.
	
	If an axial attribute of a 3D primitive is specified as a P-point, the 
	direction of the axis is taken to be the direction of the P-point, and the 
	origin of the axis to be the position of the P-point. If the axial attribute 
	is specified as a direction, the origin of the axis is taken to be the 
	component origin, i.e. the position of P-point .
	
	Examples:
	
	Syntax:
	
	\textsf{PAAX -P2 }sets PAAX to be opposite the direction of P-point 2 with 
	its origin at the position of the P-point
	
	\textsf{PBAX X34-Y }sets PBAX to the given direction from the component 
	origin
	
	\textsf{PCAX X45Y30Z }sets PCAX to the given direction from the component 
	origin
	
	\textsf{PAXI X DDANG Z }takes the Design DDANGLE and calculates the
	
	direction accordingly
	
	\begin{flushright}
		\textsf{\textgreater --}$+$\textsf{- PAXIs }--.
	\end{flushright}
	
	\textsf{\textbar \textbar }
	
	\textsf{\textbar - PAAXis -\textbar }
	
	\textsf{\textbar \textbar }
	
	\begin{flushright}
		\textsf{\textbar - PBAXis -\textbar }
	\end{flushright}
	
	\textsf{\textbar \textbar }
	
	\begin{flushright}
		\textsf{`- PCAXis -}$+$\textsf{- }\textsf{\textit{sign }}\textsf{.}
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`--------}$+$\textsf{- P }\textsf{\textit{number }}\textsf{--.}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`- \textless axis\textgreater -}$+$\textsf{- }\textsf{\textit{value 
		}}\textsf{----. \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar - \textless expres\textgreater --}$+$\textsf{- 
		}\textsf{\textit{sign }}-. \textsf{\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar `--------}$+$\textsf{- \textless axis\textgreater -\textbar 
	}
	
	\textsf{\textbar \textbar }
	
	\textsf{`---------------------------------}$+$\textsf{--\textgreater }
	
	where \textsf{\textless axis\textgreater }is
	
	\begin{flushright}
		\textsf{\textgreater --}$+$\textsf{-- X }--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar -- Y --\textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`-- Z --}$+$\textsf{--\textgreater }
	
	If the axial attribute of a 2D primitive is specified as a P-line, the 
	direction of the axis is taken to be the direction of the P-line, and the 
	origin of the axis to be the position of the P-line. If the axial attribute 
	is specified as a direction or direction expression, the origin of the axis 
	is taken to be the component origin.
	
	Examples:
	
	\textsf{PLAX PLIN NAXI }sets PLAX to be the direction of the P-line whose 
	PKEY attribute is NAXI; the origin of the axis is at the position of the 
	P-line
	
	\textsf{PLAX X60-Y }sets PLAX to the given direction from the component 
	origin
	
	Syntax:
	
	\begin{flushright}
		\textsf{\textgreater - PLAXis -}$+$\textsf{- }\textsf{\textit{sign }}-.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`--------}$+$\textsf{- PLINe \textless plkey\textgreater --.}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{`- \textless axis\textgreater -}$+$\textsf{- 
		}\textsf{\textit{value}}\textsf{----. \textbar }
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar \textbar }
	\end{flushright}
	
	\textsf{\textbar - \textless expres\textgreater -}$+$\textsf{- 
	}\textsf{\textit{sign }}-. \textsf{\textbar }
	
	\textsf{\textbar \textbar \textbar \textbar }
	
	\textsf{\textbar `--------}$+$\textsf{- \textless axis\textgreater -\textbar 
	}
	
	\textsf{\textbar \textbar }
	
	\textsf{`--------------------------------}$+$\textsf{--\textgreater }
	
	where \textsf{\textless axis\textgreater }is
	
	\begin{flushright}
		\textsf{\textgreater --}$+$\textsf{-- X }--.
	\end{flushright}
	
	\begin{flushright}
		\textsf{\textbar \textbar }
	\end{flushright}
	
	\textsf{`-- Y --}$+$\textsf{--\textgreater }
	
	and \textsf{\textless plkey\textgreater }is the PKEY attribute of the 
	P-line.
	
	\subsection{Other Uses of PARAGON}
	\label{subsec:other}
	PARAGON is used to set up:
	
	\begin{itemize}
		\item Detailing Text and Material Text
		\item Connection Tables and Bolt Tables
		\item Unit Types
		\item General Text
		\item User-defined Nominal Dimensions.
	\end{itemize}
	
	\subsection{Detailing Text}
	\label{subsubsec:detailing}
	Detailing Text (SDTE) elements contain descriptive text relating to a 
	Component, which is used during the construction of drawings, reports, 
	take-off sheets etc. An SDTE element exists at the same level in the 
	Catalogue database hierarchy as a Component element (i.e. it is a member of 
	a Section or Category) and is referred to from SPCOM elements in the 
	Specification.
	
	An SDTE element (which will usually be named) is created simply by typing, 
	for example:
	
	\textsf{NEW SDTE /C/T1}
	
	The text itself exists as an \textbf{attribute }of the SDTE element; namely 
	one of the attributes RTEX, STEX or TTEX. The text is input simply by typing 
	the attribute name followed by the text itself in quotes; for example:
	
	\textsf{STEX '21DD-JJOOA2 12.31'}
	
	The choice of attribute name depends on the PDMS module which is to use the 
	related text. STEX and TTEX are used primarily by the detailing interface 
	modules, and the attribute to be used will be specified from that module. 
	The format of the text depends on the detailing module in use - see the 
	appropriate Reference Guide for details.
	
	RTEX is used by ISODRAFT, which also uses another SDTE attribute, SKEY. SKEY 
	is a four-character code which represents a geometric description of the 
	associated Component type. RTEX and SKEY \textit{must }be set in order for ISODRAFT to 
	work correctly. A typical pair of commands would be:
	
	\textsf{RTEX 'COUPLING - SOCKET WELD 3000LB' SKEY 'COSW'}
	
	(The SKEY codes are fixed for a given element type - see the \textit{ISODRAFT Reference Guide }for a list.)
	
	\subsection{Material Text}
	\label{subsubsec:material}
	Material Text (SMTE) elements contain descriptive text describing the 
	material(s) from which the physical component is constructed, and is used 
	during the construction of drawings, reports, take-off sheets etc. An SMTE 
	element exists at the same level in the Catalogue database hierarchy as a 
	Component element (i.e. it is a member of a Section or Category) and is 
	referred to from SPCOM elements in the Specification.
	
	An SMTE element (which will usually be named) is created simply by typing, 
	for example:
	
	\textsf{NEW SMTE /5L-S-80}
	
	The text itself exists as an \textbf{attribute }of the SMTE element; namely 
	one of the attributes XTEX, YTEX or ZTEX. The text is input simply by typing 
	the attribute name followed by the text itself in quotes, for example:
	
	\textsf{XTEX 'SCM.80 API 5L GR.B SMLC'}
	
	The choice of attribute name depends on the PDMS module which is to use the 
	related text, the attribute to be used being specified from that module. 
	XTEX is used by ISODRAFT.
	
	\subsection{Connection Compatibility Tables}
	\label{subsubsec:connection}
	The Connection Compatibility Table (element name CCTA) holds a list of all 
	the compatible connection types for Piping Components in a set project. A 
	CCTA is an administrative element which exists at the same level as CATA in 
	the hierarchy. A CCTA has Connection Compatibility (COCO) elements as its 
	members, each of which has a pair of coded connection types stored as its 
	CTYPE attribute. These connection types are those referred to in the PCON 
	attribute of a Piping Component's P-points.
	
	The commands below give an example of the setting up of a typical connection 
	table.
	
	\textsf{NEW CCTA}
	
	\textsf{NEW COCO /WELDWELD CTYPE WELD WELD }(weld to weld)
	
	\textsf{NEW COCO /SCRDSCRD CTYPE SCRD SCRD }(screwed to screwed)
	
	\textsf{NEW COCO /WELDBW CTYPE WELD BW }(weld to butt weld)
	
	Note that ISODRAFT uses the connection codes to derive bolting requirements, 
	and so the connection codes used must conform to certain standards - see 
	Appendix B and the \textit{ISODRAFT Reference Guide }for details. Setting up the Connection Compatibility 
	Table should be one of the first tasks to be carried out when commencing a 
	design project using PDMS.
	
	\subsection{Bolting Tables}
	\label{subsubsec:bolting}
	The Bolt Table hierarchy contains information describing the nature of the 
	bolted connections of Piping Components in a project. Although the Bolt 
	Table is part of the Catalogue database, and so must be set up using 
	PARAGON, it has been designed for the exclusive use of ISODRAFT and so is 
	described in detail in the \textit{ISODRAFT Reference Guide}; only a summary is presented here. Element 
	creation and attribute setting is done in the usual way.
	
	The Bolt Table hierarchy is illustrated below:
	
	\begin{center}
		WORLD
	\end{center}
	
	CCTAB CATA
	
	\begin{flushright}
		SPWL
	\end{flushright}
	
	\begin{flushright}
		BLTAB
	\end{flushright}
	
	\begin{center}
		UNITS
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.01in,height=0.20in]{Paragon88}}
		\label{fig88}
	\end{figure}
	
	SECT
	
	\begin{flushright}
		BTSE
	\end{flushright}
	
	\begin{center}
		BLIST LTAB
	\end{center}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=0.01in,height=0.20in]{Paragon89}}
		\label{fig89}
	\end{figure}
	
	\begin{flushright}
		BLTP
	\end{flushright}
	
	The element types are as follows:
	
	SBOLT DTAB
	
	\begin{itemize}
		\item \textbf{BTSE }- the Bolt Set is the administrative element for catalogue component bolting information. It owns Bolt P-point (BLTP) elements.
		\item \textbf{BLTP }- the Bolt P-point stores the bolting information for an individual bolt for a particular type of flange. It has the following attributes:
	\end{itemize}
	
	NUMBER the bolt hole number in the bolt circle BDIA - the bolt diameter
	
	BTHK - the bolt length BTYPE - the type of bolt
	
	\begin{itemize}
		\item \textbf{BLTA }- the Bolt Table is an administrative element.
		\item \textbf{BLIS }- the Bolt List is an administrative element which groups together Standard Bolt (SBOL) elements.
		\item \textbf{SBOL }- the Standard Bolt element. This has the attributes:
	\end{itemize}
	
	NSTD - a pointer to a non-standard length array
	
	BITEM - additional bolt items to be used when calculating bolt length
	
	BITL - the lengths of the additional bolt items
	
	\begin{itemize}
		\item \textbf{LTAB }- the Length Table holds a number of Diameter Tables.
		\item \textbf{DTAB }- the Diameter Table stores information on standard bolt lengths, held as a string of values in its BLEN attribute. DTAB is accessed from the NSTD attribute of the SBOL element.
	\end{itemize}
	
	\subsection{Unit Types}
	\label{subsubsec:mylabel22}
	PARAGON enables unit types to be set up which will then be linked to 
	relevant attributes of the various elements which appear throughout the PDMS 
	databases. The most common units (the default units) are millimetres, inches 
	or feet and inches, which are usually assigned to bore and distance 
	attributes. These units currently apply to all PDMS modules except PROPCON.
	
	You may also define other units with conversion factors to relate one set of 
	units to another; unit definitions can be collected together into sets to be 
	used for different purposes.
	
	Information controlling units is held in a UNIT element of the Catalogue 
	Database. The UNITS hierarchy is shown below:
	
	The elements of the UNITS hierarchy are as follows:
	
	\begin{itemize}
		\item \textbf{UNIT }- The UNIT element is the top-level element of the hierarchy. It has three special attributes: BUNI, DUNI and DFUN. BUNI and DUNI can be set to determine the default Bore and Distance units, respectively. They are set to any of MM, INCH, MIL or FINC (for feet and inches). A typical sequence of setup commands would be:
	\end{itemize}
	\textsf{NEW UNIT BUNI INCH DUNI FINC}
	
	This would mean that, by default, all bore values are interpreted as inches 
	and all distance values, e.g. HEIGHT, DISTANCE, as feet and inches. If 
	user-defined units are to be used, then an MSET element should be named in 
	the DFUN attribute of the UNIT, indicating that that MSET element should be 
	used as the default measurement set.
	
	Each PDMS module has its default units initialised at run time to those 
	defined in the \textit{first }UNIT element of the \textit{first }Catalogue DB in the MDB being used. BUNI 
	and DUNI may also be set to NULL.
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{100pt}|p{47pt}|l|}
				\hline
				Output value& 
				$=$& 
				(Stored value - ADEN) / MULT \\
				\hline
				Stored value& 
				$=$& 
				(Input value * MULT) $+$ ADEN \\
				\hline
			\end{tabular}
			\label{tab18}
		\end{center}
	\end{table}
	
	\begin{itemize}
		\item \textbf{MSET }- Measurement Set. This element is used to form a collection of MTYP (measurement type) elements. It is the MSET which is named in the DFUN attribute of the UNIT element to indicate which collection of units are to be used. In practice MSET may relate to say `S.I.' or `IMPERIAL'.
		\item \textbf{MTYP }- Measurement Type. This element forms the link between a collection of attributes and the Units Definition (UDEF) to be used for them. The attributes are accessed via the ATLI (Attribute List) elements owned by the MTYP and the Units Definition via its UREF attribute. The latter simply contains the name of the UDEF element which is to be used for the attributes named in the member ATLI elements.
		\item \textbf{ATLI }- Attribute List. Each ATLI element contains (as its ATNA attribute) the name of the attribute for which the UREF (see above) applies.
		\item \textbf{USEC }- Unit Section. This is an administrative element used to collect together UDEF elements.
		\item \textbf{UDEF }- Units Definition. One UDEF is required for each non-PDMS unit that you wish to implement. UDEF has the following special attributes:
		\begin{itemize}
			\item \textbf{ABREV }- Abbreviation. This is the abbreviation used when outputting a value under the control of this UDEF, or when inputting a value which is in a UNIT that is not the one for that attribute in the current MSET. The attribute is an eight-character text.
			\item \textbf{MULT }- Multiplier. This is a conversion factor which is used in conjunction with ADEN, to convert from input/output units to PDMS stored units. This is done on the basis that:
		\end{itemize}
	\end{itemize}
	
	The exponential facility is useful in the accurate setting of MULT and ADEN. 
	For example:
	
	\textsf{MULT 0.12345 EX -8}
	
	will set MULT to 0.0000000012345
	
	\begin{itemize}
		\item \textbf{ADEN }- see MULT above.
		\item \textbf{SIGF }and \textbf{DECP }- Significant Figures and Decimal Places. These relate to the output of units.
	\end{itemize}
	To summarise, the unit is defined as:
	
	\textsf{(}\textit{input\textunderscore value }* MULT ) $+$ ADEN
	
	and is output to SIG significant figures with DEC decimal places and 
	suffixed by the notation ABREV ( e.g. `psi').
	
	\subsubsection{9.5.1 Use of Units}
	\label{para:mylabel34}
	In certain PDMS modules, e.g. PROPCON, the choice of units to be used can be 
	indicated by using the command:
	
	\textbf{UNITS }\textit{name}
	
	where \textit{name }is the name of an MSET. If this is not done, the units will be those 
	given by the DFUN attribute of the UNIT element, as explained above.
	
	Following this, whenever the value of a special attribute is set or queried, 
	its name (e.g. TEMP for temperature) will be compared with the ATNA 
	attributes of all ATLIs under the current MSET. If a match is found, then 
	the UREF of the MTYP owning the matching ATLI will be used to access the 
	relevant UDEF.
	
	When output, such values are followed by their abbreviations to remind you 
	which units are being used.
	
	If you wish to input a value which is in a UDEF that is not referred to from 
	the current MSET, then you may use the abbreviation of that value as a key. 
	For instance, in PROPCON, if the current temperature unit is centigrade, but 
	there is a UDEF defining Fahrenheit (with abbreviation `deg. F'), it would 
	appear as
	
	\textsf{TEMP 35 'deg. F'}
	
	As an example, if you require a PROPCON attribute ACBO (Actual Bore) to be 
	output in inches, then the following syntax would be required:
	
	\textsf{NEW USEC }create a new Unit Section
	
	\textsf{NEW UDEF /INCH }create and name a new Units Definition \textsf{ABREV 
		'IN' }-set ABREV and MULT attributes \textsf{MULT 0.254 EX 2}
	
	\textsf{NEW MSET }create a Measurement Set\textsf{NEW}
	
	\textsf{MTYP }create a Measurement Type
	
	\textsf{UREF /INCH }set the Reference Units that the MTYP refers to
	
	\textsf{NEW ATLI }create an Attribute List for the MTYP
	
	\textsf{ATNA ACBO }set the Attribute Name that is required to be 
	output/input in inches
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=4.78in,height=2.82in]{Paragon90}}
		\label{fig90}
	\end{figure}
	
	This results in the following hierarchy:
	
	If ACBO is referred to in PROPCON, the attribute name (ATNA) is searched for 
	in the UNIT hierarchy. The search then moves up the hierarchy to find the 
	MTYP attribute UREF. The MULT attribute of the UDEF (found from the UREF) is 
	then applied to the stored ACBO attribute and the ABREV is output with the 
	resulting value.
	
	As a further example, to define and use a unit system called /IMPERIAL, for 
	which temperatures (TEMP, PTEM and RTEM) will be in Fahrenheit and pressures 
	(PRES, RPRE and IPRE) will be in PSI, the instruction sequence would be:
	
	\textsf{NEW UNIT /EXAMPLE-OF-UNITS NEW USEC}
	
	\textsf{NEW UDEF /PSI}
	
	\textsf{ABRE 'lbf/in2' ADEN 0 MULT 6895.0 NEW UDEF /F}
	
	\textsf{ABRE 'deg. F' ADEN -17.778 MULT 0.55556 NEW MSET /IMPERIAL}
	
	\textsf{NEW MTYP /IMPERIAL/TEMP UREF /F}
	
	\textsf{NEW ATLI ATNA TEMP NEW ATLI ATNA PTEM NEW ATLI ATNA RTEM}
	
	\textsf{NEW MTYP /IMPERIAL/PRESSURE UREF /PSI}
	
	\textsf{NEW ATLI ATNA IPRE NEW ATLI ATNA RPRE NEW ATLI ATNA PRES}
	
	\textbf{NOTE: }It is possible to set up UNIT elements with MSETs containing 
	duplicated ATNAs. This is not prevented, but a warning is given on 
	attempting to use such an MSET.
	
	\subsection{General Text Elements}
	\label{subsubsec:general}
	A TEXT element is used to store additional information about an owning or 
	adjacent element. The text string itself exists as the setting of the STEX 
	attribute of the TEXT, and can be up to 120 characters long. It is set in 
	the usual way; for example
	
	\textsf{STEX 'High pressure pipeline'}
	
	Note that the STEX attribute of a TEXT element is completely independent of 
	the STEX attributes of the Detailing Text (SDTE) elements described in 
	Section 9.1. The TEXT element can occupy many positions in the hierarchy - 
	it can be owned by UNIT, CATA, SECT, CATE, STSE, STCA, CCTA, SPEC, BLTA, 
	BLIS, LTAB or MBLI elements.
	
	\subsection{User-defined Nominal Dimensions}
	\label{subsubsec:mylabel23}
	For users who required bores, bolt diameters and lengths, and rod diameters 
	that are not included in the standard nominal values stored in core, a 
	facility exists for the creation of tables that hold the required values in 
	the catalogue database.
	
	When being switched from module to module, the catalogue database is scanned 
	for a NBRWLD element with the PURP attribute set to BORE indicating that 
	user-defined nominal bores etc are to be used. If so, the nominal 
	bore-checking routine is switched to the user-defined nominal bores.
	
	\textbf{Bores}
	
	For most users, the requirement is adding or removing a few bores. For this 
	purpose, a macro of standard PDMS bores is provided (nominal\textunderscore 
	bore.mac), which enables a user to edit the values concerned and then input 
	the User-defined Nominal Bore table into the catalogue.
	
	\textbf{Bolts}
	
	When there is a need to use a bolting catalogue with both Imperial and 
	Metric projects, there is not always a direct conversion from one system to 
	the other. For example, a \textonehalf inch bolt may convert to a 12mm 
	rather than a 13mm one.
	
	To overcome the problem, User-defined Nominal Bolting tables for diameter 
	and length can be set up, as for the User-defined Nominal Bore table. The 
	PURP attribute is set to BDIA for bolt diameters and BLEN for bolt lengths.
	
	\textbf{Rods}
	
	When rods for hangers and supports are specified, the rod diameter is 
	related to the bore diameter. It is, therefore, necessary to have 
	User-defined Nominal Rod Diameter tables, if User-defined Nominal bores are 
	being used.
	
	If a hanger connects to a branch with different bores, the rod diameter is 
	selected to match the branch with the User-defined Nominal bore or, if this 
	applies to neither branch, the standard piping bore. The PURP attribute is 
	set to ROD.
	
	\textbf{Database}
	
	The following addition is made to the catalogue database: World element 
	NBRWLD, with:
	
	Attribute PURP.
	
	Owns:
	
	NOMINB elements, with:
	
	Real attribute INCBOR Inch Nominal Value Real attribute MMBOR MM Nominal 
	Value.
	
	\subsection{Datasets}
	\label{subsec:datasets}
	A Dataset (DTSE) is a collection of DATA elements. These can be used to 
	store any items of catalogue data which need to be queried directly from 
	within the DESIGN or DRAFT modules and which are not accessible by other 
	means.
	
	\subsection{Attributes of DATA Elements}
	\label{subsubsec:attributes}
	Each DATA element has the following special attributes:
	
	\textbf{DKEY Data Key}. A PDMS word which allows a specific DATA element to 
	be referenced from within DESIGN or DRAFT using the \textbf{Q PROP 
	}\textbf{\textit{dkey }}command.
	
	\textbf{PTYP Property Type}.
	
	\textbf{DTIT Data Title}. A text string describing the property stored in 
	the DATA.
	
	\textbf{PPRO Property}. Any expression which defines a property of the item 
	with which the dataset is associated.
	
	\textbf{DPRO Default Property Value}. The value to be used if the true 
	setting of the Property cannot be evaluated at any time. See Section 11.3.1.
	
	\textbf{PURP Purpose}. A PDMS word showing the purpose for which the stored 
	property is relevant. For example, PARA (for catalogue parameters), DESP 
	(for design parameters), DATA (for general properties).
	
	\textbf{NUMB Number}. An integer which may be set to further categorise the 
	specific property stored in the DATA. For example, the identifying number of 
	a PARAM or DESPARAM.
	
	\textbf{PUNI Property Units}. The units used when evaluating the Property 
	value.
	
	\textbf{RUSE Real Property Flag}. See Section 11.3.
	
	The PPRO attribute is evaluated in response to the Q PROP . . . command in 
	DESIGN or DRAFT. The parameters in the expression may not be defined until 
	the item is added to the model. It can include any attributes which are 
	valid for the design element, including user-defined attributes; for 
	example:
	
	((:COST OF OWNER) * :LENGT).
	
	The PPRO attribute can also be set to a parameterised expression which will 
	be used in the definition of Pointsets and Geomsets. See Section 11.3.
	
	\subsection{Querying Properties in DESIGN}
	\label{subsubsec:querying}
	Consider the following examples, which allow you to query two properties of 
	this parameterised \textsf{I}-beam in DESIGN:
	
	P3
	
	\begin{center}
		P1
	\end{center}
	
	\begin{center}
		P2
	\end{center}
	
	\textbf{Example 1: The depth of the beam}
	
	\textbf{Datakey}: DEPT
	
	\textbf{Dtitle}: 'Depth of beam' \textbf{Pproperty}: (PARAM [1] ) 
	\textbf{Dproperty}: 600 \textbf{Purpose}: DATA \textbf{Number: }1
	
	The command \textsf{Q PROP DEPT }in DESIGN or DRAFT will return the depth of 
	the current beam (or the default of 600 if the true value cannot be 
	evaluated).
	
	\textbf{Example 2: The cross-sectional area of the beam}
	
	\textbf{Datakey}: XSEC
	
	\textbf{Dtitle}: 'Cross--section of beam'
	
	\textbf{Pproperty}: (((P [1] - (2 * P[3])) * P[4]) $+$ (2 * (P[2] * P[3]))
	
	\textbf{NOTE: }PARAM has been shortened to P here to show the format of the 
	expression more clearly. The full version must be used when setting the 
	attribute.
	
	\textbf{Purpose}: DATA
	
	\textbf{Number}: not relevant here, so leave unset
	
	The command \textsf{Q PROP XSEC }in DESIGN or DRAFT will return the 
	calculated cross- sectional area of the current beam.
	
	\begin{flushright}
		\textit{Datasets}
	\end{flushright}
	
	Similarly, you could query the following attributes of this DATA element:
	
	\textsf{Q PRTI XSEC }Data title
	
	\textsf{Q PRDE XSEC }Data description
	
	\textsf{Q PRPU XSEC }Data purpose
	
	\subsection{Real Properties of P-points, P-Lines and Geomsets}
	\label{subsubsec:mylabel24}
	Pointset and Geomset attributes can be defined in terms of a Dataset 
	pseudo-attribute RPROP (Real Property). For example, the PBORE of a P-point 
	can be defined by the expression:
	
	\textbf{PBORE ( PARAM[1] }$+$\textbf{ 20 )}
	
	If the dataset associated with the component contains a DATA element with 
	the Datakey DBOR, and DBOR has its PPRO attribute set to the expression ( 
	PARAM[1] $+$ 20 ), PBORE can be defined as:
	
	\textbf{PBORE ( RPROP DBOR )}
	
	Pointset and Geomsets with attributes defined in terms of RPROPs will have 
	their RFLG flag set to 1. Only elements with RFLG set to 1 need to be 
	pre-evaluated when the item is added to a model.
	
	DATA elements have an attribute RUSE. If this attribute is set, the PROP 
	attribute (or default Property DPRO, see Section 11.3.1) cannot be set to a 
	text expression or to an expression containing the OF notation. RUSE is set 
	($=$1) and unset ($=$0) using the commands:
	
	\textbf{SETRuse UNSETRuse}
	
	DATA elements with PROP attributes property which can be used as RPROPs 
	should have their RUSE flags set. Only elements with RUSE set to 1 need to 
	be pre-evaluated.
	
	\subsubsection{Default Values}
	\label{para:default}
	The DATA element attribute DPRO can be used to store a default property 
	value. When a Design element is added to the model, the associated dataset 
	is pre-evaluated and the default value used if the PPRO attribute in the 
	Dataset unset or cannot be evaluated.
	
	The default property value can be queried from DESIGN using the 
	pseudo-attribute PRDE.
	
	\subsubsection{Querying}
	\label{para:querying}
	The value of RPROP can be queried using the command:
	
	\textbf{Q RPROP }\textit{datakey}
	
	This command will return the result `RPROP unset' if the corresponding PPRO 
	attribute contains a text string rather than a real value.
	
	The default value of a text or real property value may be queried from a 
	Design component using the command:
	
	\textbf{Q PRDE }\textit{datakey}
	
	A list of the datakeys available at a Design item can be obtained using the 
	command:
	
	\textbf{Q PRLS}
	
	\subsection{Checking Catalogue Database Consistency}
	\label{subsec:checking}
	To avoid having to transfer component design or specification errors from 
	the Catalogue database to the Design database before data inconsistencies 
	can be detected, a facility is provided for checking the main settings of a 
	piping catalogue as you build it in PARAGON. (This facility is not yet 
	available for checking a structural catalogue.)
	
	\subsection{Initiating a Standard Data Consistency Check}
	\label{subsubsec:initiating}
	The basic command to initiate a database consistency check, using default 
	settings, is
	
	\textbf{CHECK \textless gid\textgreater }
	
	where \textless gid\textgreater , the element below which checks are to be 
	carried out, may be any SPEC, SELE, SPCO or COMP.
	
	If you start the check from within a specification (SPEC, SELE or SPCO) all 
	components referenced via the starting element will be checked. If you start 
	the check at component level (COMP), only that component and elements below 
	it will be checked.
	
	(See Section 13.3 for details of the ways in which you can modify the 
	default checking procedures.)
	
	\subsection{What the Checking Facility Does}
	\label{subsubsec:mylabel25}
	The following tests may be carried out:
	
	\textbf{At SPEC level:}
	
	\begin{itemize}
		\item Check that no question in the specification is repeated.
		\item Check that one question in the specification is TYPE.
		\item From the TYPE reference, check that the GTYPE of the COMP has the same setting.
		\item From the TYPE reference, check that the SKEY setting of SDTE is correct.
		\item From the TYPE reference, check that the point set has the correct geometry, as required by ISODRAFT.
	\end{itemize}
	
	\textbf{At SPCO level:}
	
	\begin{itemize}
		\item Check that all of the following reference attributes are set: CATREF, DETAIL, MATX, CMPR, BLTREF. (The BLTREF need be set only if the connection type begins with F or L.)
	\end{itemize}
	
	\textbf{At COMP or equivalent level:}
	
	\begin{itemize}
		\item Check that there is a valid PTREF and GMREF.
		\item At a PTSE, check that P-points are set and that there are no duplicate numbers.
		\item At a GMSE, check that there are primitives set and that they are not degenerate. Check also that no invalid P-point numbers or parameters are used. Note that this test uses catalogue parameters, so that if a primitive is constructed only from design and insulation parameters, spurious warnings will be generated.
		\item Check that each P-point connection type exists in the COCO tables. P-points used for construction purposes can have connections of 0.0, NUL or NULL. The connection type will not be checked for validity for a specific type of component.
		\item Check that a P-point bore is valid for a recognised set of nominal bores. P-points used for construction purposes, and a P-point with connection type CLOS, can have a zero bore.
	\end{itemize}
	
	\subsection{Controlling the Detailed Checking Procedure}
	\label{subsubsec:controlling}
	You can modify the effect of the \textbf{CHECK }command by using additional 
	syntax so that you can check different types of catalogue without generating 
	unnecessary errors.
	
	The command options are as follows:
	
	\textbf{TOLerance CATAlogue CMPRef ON/OFF}
	
	switches Component Reference checking on or off for all component types in a 
	SPCO.
	
	\textbf{TOLerance CATAlogue CMPRef }\textit{word }\textbf{ON/OFF}
	
	switches Component Reference checking on or off for the specified component 
	type in a SPCO.
	
	\textbf{TOLerance CATAlogue GMREf ON/OFF}
	
	switches Geomset Reference checking on or off for all component types.
	
	\textbf{TOLerance CATAlogue GMREf }\textit{word }\textbf{ON/OFF}
	
	switches Geomset Reference checking on or off for the specified component 
	type.
	
	\textbf{TOLerance CATAlogue BORE ON/OFF}
	
	switches bore checking on or off for Pointsets.
	
	\textbf{TOLerance CATAlogue BORE }\textit{value value}
	
	sets range of permissible bores to be checked for Pointsets.
	
	\textbf{TOLerance CATAlogue ISOMetric ON/OFF}
	
	checks for SKEY and similar ISODRAFT--related settings.
	
	\textbf{TOLerance CATAlogue DEFault}
	
	resets all checking options to their default settings.
	
	\textit{Checking Catalogue Database Consistency}
	
	These defaults are:
	
	\begin{itemize}
		\item Do not check any CMPREFs.
		\item Ignore GMREF settings for ATTA, FLAN, TUBE and BOLT.
		\item Check nominal bores in the range 6 mm to 2150 mm.
		\item Check all ISODRAFT-related settings.
	\end{itemize}
	
	To query any of the current data consistency checking settings, use the 
	corresponding command format
	
	\textbf{Q TOLerance CATAlogue ...}
	
	\subsection{Error Messages}
	\label{subsubsec:error}
	Error messages which can result from diagnosed data inconsistencies are as 
	follows: \textsf{C10 Spec error: Question }\textit{word }\textsf{asked more than once C20 
		Spec error: Question TYPE never asked}
	
	\textsf{C30 Spco error: DETA not set}
	
	\textsf{C40 Spco error: Unknown ref for DETA C50 Spco error: MATX not set}
	
	\textsf{C60 Spco error: Unknown ref for MATX C70 Spco error: CMPR not set}
	
	\textsf{C80 Spco error: Unknown ref for CMPR C90 Spco error: BLTR not set}
	
	\textsf{C100 Spco error: Unknown ref for BLTR C110 Spco error: CATR not set}
	
	\textsf{C120 Spco error: Unknown ref for CATR C130 Comp error: PTRE not set}
	
	\textsf{C140 Comp error: Unknown ref for PTRE C150 Comp error: GMRE not set}
	
	\textsf{C160 Comp error: Unknown ref for GMRE}
	
	\textsf{C170 Ptset error: Duplicate ppoint number }\textit{integer}
	
	\textsf{C180 Ptset error: No ppoints set}
	
	\textsf{C190 Ptset error: Unknown connection type }\textit{word }\textsf{for }\textit{ppoint}
	
	\textsf{C200 Comp error: GTYPE }\textit{word }\textsf{different from spec TYPE}
	
	\textit{word}
	
	\textsf{C210 Ptset error: Non standard bore }\textit{value }\textsf{for }\textit{ppoint}
	
	\textsf{C220 Gmset error: Unknown parameter }\textit{integer }\textsf{for }\textit{primitive}
	
	\textsf{C230 Gmset error: Axis defined with unknown Ppoint}\textit{integer }\textsf{for 
	}\textit{primitive}
	
	\textsf{C240 Isometric error: Ppoint}\textit{integer }\textsf{not defined}
	
	\textsf{C250 Isometric error: Cannot calculate angle between Ppoint}\textit{integer }\textsf{and 
		Ppoint}\textit{integer}
	
	\textsf{C260 Isometric error: Incorrect angle between Ppoint}\textit{integer }\textsf{and 
		Ppoint}\textit{integer}\textsf{. Angle is }\textit{value }\textsf{and should be }\textit{value}.
	
	\textsf{C270 Isometric error: Incorrect angle between Ppoint}\textit{integer }\textsf{and 
		Ppoint}\textit{integer}\textsf{. They should not be parallel.}
	
	\textsf{C280 Gmset error: }\textit{primitive }\textsf{may be a degenerate primitive C290 
		Isometric error: Ppoint1, Ppoint2 and Ppoint0}
	
	\textsf{should be colinear}
	
	\textsf{C300 Gmset error: }\textit{primitive }\textsf{cannot be constructed C310 Gmset error: 
		Expression error for }\textit{primitive }\textsf{C820 SKEY not set}
	
	\textsf{C830 SKEY }\textit{word }\textsf{is used with generic type }\textit{word}\textsf{, not }\textit{word}
	
	\textsf{C840 SKEY }\textit{word }\textsf{not known. Assumed to be user defined.}
	
	\subsection{P-point Conventions for Piping Components}
	\label{subsec:mylabel1}
	You must use the following conventions for numbering the P-points of Piping 
	Components so that ISODRAFT can recognise them:
	
	\begin{itemize}
		\item For \textbf{tube components}, there must only be one P-point, P1, which defines the bore and connection type of both ends of the piece of tube.
		\item For \textbf{nozzles}, the connection P-point (i.e. the P-point for connection to the head or tail branch) must be P1.
		\item For \textbf{two-way components}, the arrive and leave P-points must be numbered P1 and P2 (in either order). For \textbf{two-way valves}, the spindle direction must be indicated by P3.
		\item For \textbf{three-way components}, the offline leg must be indicated by P3. The spindle direction for \textbf{three-way valves }must be specified by using a P-point greater than P3, which must have its bore unset.
		\item For \textbf{four-way components}, the two straight-through flows must have P-points P1/P2 and P3/P4. The spindle direction for \textbf{four-way valves }must be specified by using a P-point greater than P4, which must have its bore unset.
		\item For \textbf{eccentric reducers without a connection point}, the flat side must be indicated by P3. \textbf{Eccentric reducers with a connection point }must use P3, with a valid bore set, to indicate the connection point and must use P9, with bore unset, for orientation of the flat side.
		\item For \textbf{U-bends}, the P-points must be set as shown in Figure A-1.
	\end{itemize}
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=6.31in,height=0.01in]{Paragon91}}
		\label{fig91}
	\end{figure}
	
	\begin{center}
		P4 P3 P5
	\end{center}
	
	\begin{center}
		P1 P2
	\end{center}
	
	\textbf{Figure A-1 }P-point Numbering Convention for U-bends See the 
	\textit{ISODRAFT Reference Manual }for further details.
	
	\subsection{Setting Up a Catalogue}
	\label{subsec:setting}
	\subsection{Naming Conventions}
	It is important that certain items in the Catalogue database are named as 
	they are referenced from other databases as well as internally. It would be 
	impracticable to allow system-generated database reference numbers to be 
	referenced as this would lead to meaningless output from reports and 
	isometrics.
	
	Figure B-1 shows the relationship between the Design, Specification, and 
	Catalogue databases. Consistency when naming items is important, making 
	cross-database connections as easily identifiable as possible.
	
	In ISODRAFT, bolt lengths for Piping Components are derived by referring to 
	the SBOL name. Item detail is picked up from the RTEX attribute of the DTEX 
	and the material is picked up from the XTEX attribute of the MTEX.
	
	Note that the item code name on an isometric is obtained from the \textit{second }part of 
	the SPREF attribute of a Component, i.e. its name in the Specification. In 
	the example in Figure B-1, the name would be output as FLANWN300100. See the 
	\textit{ISODRAFT Reference Manual }for further details.
	
	\subsection{Example Connection Type Codes}
	Naming of the P-point PCON attribute of a Piping Component requires early 
	consideration. The PCON name is for use mainly in data consistency checking, 
	but also by ISODRAFT for working out bolting details. The rules for ISODRAFT 
	are as follows:
	
	\begin{itemize}
		\item The first letter of the PCON attribute of a flange must be `F' or `L' (the latter for lap joints)
		\item The first letter of the PCON attribute of a gasket must be `G'
		\item The first letter of the PCON attribute of a wafer fitting must be `W'
	\end{itemize}
	
	The list below is not exhaustive and only shows example codes - it is not 
	mandatory.
	
	\textbf{Item and/or Connection Type Code}
	
	300lb Raised-Face Flange FGD
	
	300lb Gasket GGD
	
	Pipe Bevelled End TUB
	
	Butt Weld BWD
	
	Socket Weld SWF
	
	300lb Wafer Fitting WGD
	
	Screwed Male SCM
	
	Screwed Female SCF
	
	\begin{flushright}
		\textit{Setting Up a Catalogue}
	\end{flushright}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=5.33in,height=8.85in]{Paragon92}}
		\label{fig92}
	\end{figure}
	
	\subsection{The Connection Compatibility Table}
	\label{subsubsec:mylabel26}
	The table in the previous section can be used to construct a PDMS Connection 
	Compatibility Table (CCTA) which sets out all the permissible connection 
	pairs.
	
	If an attempt is made to connect two pipework components in DESIGN, then a 
	check is made to see if the p-leave PCON attribute of the first component 
	and the p-arrive PCON attribute of the second component appear as a matching 
	pair in the connection table. If there is such a matching pair then the 
	components are connected, otherwise a similar check is made on the p-leave 
	PCON attributes of each component. If a matching pair is now found, the 
	second component is `flipped' and connected to the first. If no matching 
	pair is found then an `\textsf{incompatible connection type}' error message 
	is output and the second component is left in its original position and 
	orientation.
	
	The following sample connection table uses the connection list given in the 
	previous section:
	
	\textsf{NEW CCTAB}
	
	\textsf{NEW COCO /FGDGGD CTYPE FGD GGD NEW COCO /TUBBWD CTYPE TUB BWD NEW 
		COCO /GGDWGD CTYPE GGD WGD NEW COCO /TUBSWF CTYPE TUB SWF NEW COCO /SCMSWF 
		CTYPE SCM SWF NEW COCO /SCFTUB CTYPE SCF TUB}
	
	The COCO (Connection Compatibility) elements are named so that the allowable 
	connections are easily queried.
	
	The above table shows, for example, that tube can be connected to a screwed 
	female connection but not to a screwed male connection.
	
	Different ratings of flanges and gaskets should have different connection 
	attributes to ensure that different pressure fittings cannot be connected 
	without a warning message being issued. This principle also applies to 
	different flange face characteristics, e.g. flat face and raised face: 
	however, there are some exceptions. On some jobs a flat-faced flange on a 
	piece of equipment may be butted up to a raised-face flange. If this is a 
	common occurrence, it may be worth inputting a new COCO to allow the 
	connection.
	
	\subsection{Construction of Typical Piping Components}
	\label{subsec:construction}
	This Appendix gives sample macros for the construction of typical Catalogue 
	Piping Components using PARAGON.
	
	Each macro starts at CATEGORY level. The view parameters used to produce the 
	drawings shown vary between each example, and so are not given here. Each 
	drawing has REPRESENTATION settings of TUBE ON CENTRELINE ON PPOINTS ON
	
	NUMBERS ON. Some of the Components are too large to fit onto a typical view 
	area when drawn at the default SCALE value of 1. Values of 0.5 are suggested 
	for examples 1 and 3, and 0.05 for example 6.
	
	The definition for each Component includes the possibility of insulation 
	being present, although this is not drawn. Note how the clash geometry and 
	component geometry have been combined.
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=11.73in,height=10.14in]{Paragon93}}
		\label{fig93}
	\end{figure}
	
	\textbf{Figure C-1 }A Control Valve, using the SDSH primitive
	
	\textsf{NEW PTSE /CVMWPS NEW GMSE /CVMWGS NEW SCOM /CVMW}
	
	\textsf{GTYP INST PARA 25 100 133 17.5 FLGD PTRE /CVMWPS}
	
	\textsf{GMRE /CVMWGS MODEL CE GOTO PTRE NEW PTAX}
	
	\textsf{PCON (PARAM[5]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[2]) PAXI -Y}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON (PARAM[5]) NUMB 2 PBOR (PARAM[1]) PDIS (PARAM[2]) PAXI Y}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON NULL NUM 3 PBOR 0 PDIS (2.50 * PARAM[4]) PAXI X}
	
	\textsf{/CVMW GOTO GMRE NEW SCYL}
	
	\textsf{PDIS (PARAM[2]) PHEI (-2 * PARAM[2]) PDIA (PARAM[3]) PAXI Y NEW 
		SCYL}
	
	\textsf{PDIS 0 PHEI (2.5 * PARAM[2]) PDIA (1.6 * PARAM[2]) PAXI X NEW SSPH}
	
	\textsf{OBST 0 CLFL TRUE TUFL TRUE PDIS 0 PAXI -Y PDIA (0.50 * PARAM[1]) NEW 
		SCON}
	
	\textsf{OBST 0 CLFL TRUE TUFL TRUE PDIS (2.5 * PARAM[2]) PDIA (1.6 * 
		PARAM[2])}
	
	\textsf{PAXI X NEW SDSH}
	
	\textsf{CLFL TRUE TUFL TRUE PDIA (1.6 * PARAM[2]) PHEI (0.8 * PARAM[2]) PDIS 
		(2.5 * PARAM[2]) PAXI X}
	
	\textsf{NEW SCYL}
	
	\textsf{OBST 0 TUFL TRUE PDIS (PARAM[2]) PHEI (-1 * PARAM[4]) PDIA (PARAM[3] 
	}$+$\textsf{ IPARAM[1]) PAXI -Y}
	
	\textsf{NEW SCYL COPY PREV PAXI Y}
	
	\textsf{OBST 0 TUFL TRUE PDIS (PARAM[2]) PHEI (-1.0 * PARAM[4]) PDIA 
		(PARAM[3] }$+$\textsf{ IPARAM[1]) PAXI Y}
	
	\textsf{NEW LSNO}
	
	\textsf{OBST 0 TUFL TRUE PTDI (PARAM[2] - PARAM[4]) PBDI 0 PTDM (PARAM[3] 
	}$+$\textsf{ IPARAM[1]) PBDM (1 }$+$\textsf{ IPARAM[1]) PAAX -Y PBAX Z}
	
	\textsf{NEW LSNO COPY PREV PAAX Y NEW LSNO}
	
	\textsf{OBST 0 CLFL TRUE PTDI (PARAM[2]) PBDI 0}
	
	\textsf{PTDM (PARAM[3] }$+$\textsf{ IPARAM[1]) PBDM (1 }$+$\textsf{ 
		IPARAM[1]) PAAX -Y PBAX Z}
	
	\textsf{NEW LSNO COPY PREV PAAX Y}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=14.53in,height=10.40in]{Paragon94}}
		\label{fig94}
	\end{figure}
	
	\begin{center}
		\textbf{Figure C-2 }An Unequal Tee
	\end{center}
	
	\textsf{NEW PTSE /MWTPTSET NEW GMSE /MWTGMSET NEW SCOM /MWNEQTEE}
	
	\textsf{GTYP TEE PARA 100 80 114 90 BWD 105 80 15 10 PTRE /MWTPTSET}
	
	\textsf{GMRE /MWTGMSET MODEL CE}
	
	\textsf{GOTO PTRE NEW PTAX}
	
	\textsf{PCON (PARAM[5]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[6]) PAXI -Y}
	
	\textsf{NEW PTAX COPY PREV PAXI Y NUM 2 NEW PTAX}
	
	\textsf{PCON (PARAM[5]) NUMB 3 PBOR (PARAM[2]) PDIS (PARAM[7]) PAXI X}
	
	\textsf{/MWNEQTEE GOTO GMRE NEW LINE}
	
	\textsf{OBST 0 CLFL TRUE P1 P2 NEW LINE}
	
	\begin{center}
		C-4 VANTAGE PDMS PARAGON
	\end{center}
	
	\textsf{OBST 0 CLFL TRUE P3 P0 NEW SSPH}
	
	\textsf{OBST 0 CLFL TRUE PDIS 0 PAXI P1 PDIA (PARAM[8]) NEW SSPH}
	
	\textsf{COPY PREV PAXI P2 NEW SSPH}
	
	\textsf{OBST 0 CLFL TRUE LEVE 0 2 PDIS 0 PAXI P3 PDIA (PARAM[9])}
	
	\textsf{NEW SCYL}
	
	\textsf{TUFL TRUE PDIS 0 PHEI (-2 * PARAM[6]) PDIA (PARAM[3]) PAXI P1}
	
	\textsf{NEW SCYL}
	
	\textsf{TUFL TRUE PDIS 0 PHEI (PARAM[7]) PDIA (PARAM[4]) PAXI X}
	
	\textsf{END}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=11.81in,height=11.12in]{Paragon95}}
		\label{fig95}
	\end{figure}
	
	\begin{center}
		\textbf{Figure C-3 }A Weld Neck Flange
	\end{center}
	
	\textsf{NEW PTSE /MWFLPS NEW GMSE /MWFLGS NEW SCOM /MWWNFLAN}
	
	\textsf{GTYP FLAN PARA 100 114 254 30 56 180 TUB FLGD 20 PTRE /MWFLPS}
	
	\textsf{GMRE /MWFLGS MODEL CE GOTO PTRE NEW PTAX}
	
	\textsf{PCON (PARAM[8]) NUMB 1 PBOR (PARAM[1]) PDIS 0 PAXI -Y}
	
	\begin{center}
		C-6 VANTAGE PDMS PARAGON
	\end{center}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON (PARAM[7]) NUMB 2 PBOR (PARAM[1]) PAXI Y PDIS (PARAM[4] 
	}$+$\textsf{ PARAM[5])}
	
	\textsf{/MWWNFLAN GOTO GMRE NEW SCYL}
	
	\textsf{CLFL TRUE TUFL TRUE PDIS 0 PHEI (PARAM[4]) PDIA (PARAM[3] 
	}$+$\textsf{ IPARAM[1]) PAXI Y}
	
	\textsf{NEW LINE}
	
	\textsf{OBST 0 CLFL TRUE P1 P2 NEW SSPH}
	
	\textsf{OBST 0 CLFL TRUE PDIS 0 PAXI P2 PDIA (PARAM[9]) NEW LSNO}
	
	\textsf{TUFL TRUE PTDI (PARAM[5] }$+$\textsf{ PARAM[4])}
	
	\textsf{PBDI (PARAM[4]) PBDM (PARAM[6] }$+$\textsf{ IPARAM[1])}
	
	\textsf{PTDM (PARAM[2] }$+$\textsf{ IPARAM[1]) PAAX Y PBAX X POFF 0 END}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=10.53in,height=9.10in]{Paragon96}}
		\label{fig96}
	\end{figure}
	
	\begin{center}
		\textbf{Figure C-4 }A Concentric Reducer
	\end{center}
	
	\textsf{NEW PTSE /MWRPTSET NEW GMSE /MWRGMSET NEW SCOM /MWCR2}
	
	\textsf{GTYP REDU PARA 100 80 110 90 102 0 BWD 15 10 PTRE /MWRPTSET}
	
	\textsf{GMRE /MWRGMSET MODEL CE}
	
	\textsf{GOTO PTRE NEW PTAX}
	
	\textsf{NUMB 1 PCON (PARAM[7]) PBOR (PARAM[1]) PDIS 0 PAXI -Y NEW PTCA}
	
	\textsf{NUMB 2 PCON (PARAM[7]) PBOR (PARAM[2]) PX 0 PY (PARAM[5]) PZ (-1 * 
		PARAM[6])}
	
	\textsf{NEW PTAX}
	
	\textsf{NUMB 3 PDIS 0 PAXI -Z}
	
	\textsf{/MWCR2}
	
	\begin{center}
		C-8 VANTAGE PDMS PARAGON
	\end{center}
	
	\textsf{GOTO GMRE NEW LINE}
	
	\textsf{OBST 0 CLFL TRUE P1 P2}
	
	\textsf{NEW SSPH OBST 0 CLFL TRUE PDIS 0 PAXI P1 PDIA (PARAM[8])}
	
	\textsf{NEW SSPH OBST 0 CLFL TRUE PDIS 0 PAXI P2 PDIA (0.65 * PARAM[9]) NEW 
		LSNO}
	
	\textsf{TUFL TRUE PTDI (PARAM[5])}
	
	\textsf{PBDI 0 PTDM (PARAM[4] }$+$\textsf{ IPARAM[1]) PBDM (PARAM[3] 
	}$+$\textsf{ IPARAM[1])}
	
	\textsf{PAAX Y PBAX -Z POFF (PARAM[6]) END}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=11.02in,height=8.39in]{Paragon97}}
		\label{fig97}
	\end{figure}
	
	\begin{center}
		\textbf{Figure C-5 }An Elbow
	\end{center}
	
	\textsf{NEW PTSE /MWPS35 NEW GMSE /MWGS34 NEW SCOM /MWEL5}
	
	\textsf{GTYP ELBO PARA 50 60 25 75 15 SWF PTRE /MWPS35}
	
	\textsf{GMRE /MWGS34 MODEL CE GOTO PTRE NEW PTAX}
	
	\textsf{PCON (PARAM[6]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[3]) PAXI -Y}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON (PARAM[6]) NUMB 2 PBOR (PARAM[1]) PDIS (PARAM[3]) PAXI Y 45 X}
	
	\textsf{/MWEL5 GOTO GMRE NEW LINE}
	
	\textsf{OBST 0 CLFL TRUE P1 T0 P2 NEW SCTO}
	
	\textsf{TUFL TRUE PAAX P1 PBAX P2 PDIA (PARAM[2] }$+$\textsf{ IPARAM[1])}
	
	\textsf{NEW LSNO}
	
	\textsf{OBST 0 CLFL TRUE PTDI (PARAM[5]) PBDI 0.00 PTDM (PARAM[4] 
	}$+$\textsf{ IPARAM[1])}
	
	\textsf{PBDM (PARAM[4] }$+$\textsf{ IPARAM[1]) PAAX P1 PBAX Z TVIS FALSE NEW 
		LSNO COPY PREV PAAX P2}
	
	\textsf{NEW SCYL OBST 0}
	
	\textsf{TUFL TRUE PHEI (PARAM[5])}
	
	\textsf{PDIA (PARAM[4] }$+$\textsf{ IPARAM[1]) PAXI P1 NEW SCYL COPY PREV 
		PAXI P2}
	
	\textsf{END}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=13.03in,height=12.87in]{Paragon98}}
		\label{fig98}
	\end{figure}
	
	\begin{center}
		\textbf{Figure C-6 }A Mitred Elbow, using SSLC Primitives
	\end{center}
	
	\textsf{NEW PTSE /MWPTESTC1 NEW GMSE /MWGTESTC1 NEW SCOM /MWLOBST-51}
	
	\textsf{GTYP ELBO PARA 500 2000 398.7 -550 -152.2 -1234.6 -585.5 BWDN PTRE 
		/MWPTESTC1}
	
	\textsf{GMRE /MWGTESTC1 MODEL CE}
	
	\textsf{GOTO PTRE NEW PTAX}
	
	\textsf{PCON (PARAM[8]) NUMB 1 PBOR (PARAM[1]) PDIS (PARAM[2])}
	
	\begin{center}
		C-12 VANTAGE PDMS PARAGON
	\end{center}
	
	\textsf{PAXI -Y NEW PTAX}
	
	\textsf{PCON (PARAM[8]) NUMB 2 PBOR (PARAM[1]) PDIS (PARAM[2]) PAXI X}
	
	\textsf{NEW PTCA}
	
	\textsf{NUMB 3 PX (-PARAM[6]) PY (PARAM[5]) PZ 0 PTCDIR -X 24 -Y}
	
	\textsf{NEW PTCA}
	
	\textsf{NUMB 4 PX (-PARAM[7]) PY (PARAM[7]) PZ 0 PTCDIR -X 45 -Y}
	
	\textsf{NEW PTCA}
	
	\textsf{NUMB 5 PX (-PARAM[5]) PY (PARAM[6]) PZ 0 PTCDIR -Y 24 -X}
	
	\textsf{/MWLOBST-51 GOTO GMRE NEW SRTO}
	
	\textsf{PAAX P1 PBAX P2}
	
	\textsf{PDIA (-1.2 * PARAM[4]) PHEI (PARAM[3])}
	
	\textsf{NEW SSLC OBST }0
	
	\textsf{CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-PARAM[3]) PDIS 0 PAXI P1 
		PXTS -11.5}
	
	\textsf{NEW SSLC OBST 0}
	
	\textsf{CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-PARAM[3]) PDIS 0 PAXI P2 
		PXTS 11.5}
	
	\textsf{NEW SSLC OBST 0}
	
	\textsf{CLFL TRUE TUFL TRUE PDIA (PARAM[4]) PHEI (-2 * PARAM[3]) PDIS 
		(PARAM[3]) PAXI P3 PXTS -11.5 PXBS 11.5}
	
	\textsf{NEW SSLC COPY PREV PAXI P4 NEW SSLC COPY PREV PAXI P5 END}
	
	\textsf{{\$}.}
	
	\begin{figure}[htbp]
		\centerline{\includegraphics[width=17.54in,height=7.75in]{Paragon99}}
		\label{fig99}
	\end{figure}
	
	\textbf{Figure C-7 }A Rectangular Cross Section Pipe, using BOXI primitives
	
	\textbf{PARAGON Syntax}:
	
	\textsf{NEW PTSE /PBOXI2 NEW PTAX}
	
	\textsf{PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 0 PAXI -Y END OF END}
	
	\textsf{NEW GMSE /GBOXI2 NEW BOXI}
	
	\textsf{PAXI P1 PXLE (PARAM[3]) PZLE (PARAM[2]) CLFL TRUE TUFL TRUE END OF 
		END}
	
	\textsf{NEW PTSE /PELBO NEW PTAX}
	
	\textsf{PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 250 PAXI -Y}
	
	\textsf{END}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 250 PAXI X}
	
	\textsf{END OF END}
	
	\textsf{NEW GMSE /GELBO NEW SRTO}
	
	\textsf{CLFL TRUE TUFL TRUE PAAX P1 PBAX P2 PDIA (PARAM[2]) PHEI (PARAM[3])}
	
	\textsf{END OF END}
	
	\textsf{NEW PTSE /PVELBO NEW PTAX}
	
	\textsf{PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 250 PAXI -Y}
	
	\textsf{END}
	
	\textsf{NEW PTAX}
	
	C-14 VANTAGE PDMS PARAGON
	
	\textsf{PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 250 PAXI Z}
	
	\textsf{END OF END}
	
	\textsf{NEW PTSE /PWELD NEW PTAX}
	
	\textsf{PCON BWD NUM 1 PBOR (PARAM[1]) PDIS 0 PAXI Y END}
	
	\textsf{NEW PTAX}
	
	\textsf{PCON BWD NUM 2 PBOR (PARAM[1]) PDIS 0 PAXI -Y END OF END}
	
	\textsf{NEW GMSE /GWELD NEW SSPH}
	
	\textsf{CLFL TRUE TUFL TRUE PAXI P1 PDIA (PARAM[2]) END OF END}
	
	\textsf{NEW SCOM /BOX100}
	
	\textsf{GTYP TUBE PARA 300100 100 300 END}
	
	\textsf{OLD SCOM /BOX100}
	
	\textsf{PTRE PTSE /PBOXI2 GMRE GMSE /GBOXI2 NEW SCOM /HELBO100}
	
	\textsf{GTYP ELBO PARA 300100 300 100 END}
	
	\textsf{OLD SCOM /HELBO100}
	
	\textsf{PTRE /PELBO GMRE /GELBO NEW SCOM /VELBO100}
	
	\textsf{GTYP ELBO PARA 300100 100 300 END}
	
	\textsf{OLD SCOM /VELBO100}
	
	\textsf{PTRE /PVELBO GMRE /GELBO NEW SCOM /BWELD100}
	
	\textsf{GTYP WELD PARA 300100 200 END}
	
	\textsf{OLD SCOM /BWELD100}
	
	\textsf{PTRE /PWELD GMRE /GWELD}
	
	\textbf{SPECON Macro}:
	
	\textsf{NEW SPECIFICATION /BOXI.SPEC MATREF }$=$\textsf{0}
	
	\textsf{FLUREF }$=$\textsf{0}
	
	\textsf{RATING 0.000}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{179pt}|p{60pt}|p{54pt}|p{89pt}|}
				\hline
				\textsf{LINETYPE NUL}& 
				\multicolumn{3}{|p{203pt}|}{} \\
				\hline
				\textsf{HEADING} \par \textsf{TYPE NAME PBOR0}& 
				\textsf{CATREF}& 
				\textsf{DETAIL}& 
				\textsf{MATXT CMPREF} \\
				\hline
				\textsf{BLTREF} \par \textsf{TUBE */D300X100 300100.0}& 
				\textsf{/BOX101}& 
				\textsf{}$=$\textsf{0}& 
				\textsf{}$=$\textsf{0 }$=$\textsf{0} \\
				\hline
				\textsf{}$=$\textsf{0}& 
				& 
				& 
				\\
				\hline
			\end{tabular}
			\label{tab19}
		\end{center}
	\end{table}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{107pt}|p{59pt}|p{38pt}|p{68pt}|p{44pt}|p{32pt}|p{35pt}|}
				\hline
				\textsf{HEADING} \par \textsf{TYPE NAME}& 
				\textsf{PBOR0}& 
				\textsf{STYP}& 
				\textsf{CATREF}& 
				\textsf{DETAIL}& 
				\textsf{MATXT}& 
				\textsf{CMPRE} \\
				\hline
				\textsf{BLTREF} \par \textsf{ELBO */HB300X100}& 
				\textsf{300100.0}& 
				\textsf{H}& 
				\textsf{/HELBO101}& 
				\textsf{}$=$\textsf{0}& 
				\textsf{}$=$\textsf{0}& 
				\textsf{}$=$\textsf{0} \\
				\hline
				\textsf{}$=$\textsf{0} \par \textsf{ELBO */VB300X100}& 
				\textsf{300100.0}& 
				\textsf{V}& 
				\textsf{/VELBO101}& 
				\textsf{}$=$\textsf{0}& 
				\textsf{}$=$\textsf{0}& 
				\textsf{}$=$\textsf{0} \\
				\hline
				\textsf{}$=$\textsf{0}& 
				& 
				& 
				& 
				& 
				& 
				\\
				\hline
				\textsf{HEADING}& 
				& 
				& 
				& 
				& 
				& 
				\\
				\hline
				\textsf{TYPE NAME BLTREF} \par \textsf{WELD */W300X100}& 
				\textsf{PBOR0} \par \textsf{300100.0}& 
				\multicolumn{2}{|p{107pt}|}{\textsf{CATREF DETAIL} \par \textsf{/BWELD101 }$=$\textsf{0}} & 
				\textsf{MATXT} \par \textsf{}$=$\textsf{0}& 
				\multicolumn{2}{|p{68pt}|}{\textsf{CMPREF} \par \textsf{}$=$\textsf{0}} \\
				\hline
				\textsf{}$=$\textsf{0} \par \textsf{{\$}.}& 
				& 
				\multicolumn{2}{|p{107pt}|}{} & 
				& 
				\multicolumn{2}{|p{68pt}|}{} \\
				\hline
			\end{tabular}
			\label{tab20}
		\end{center}
	\end{table}
	
	\textbf{DESIGN Syntax}:
	
	\textsf{NEW PIPE}
	
	\textsf{SPEC BOXI.SPEC}
	
	\textsf{NEW BRAN /BOXIBRAN}
	
	\textsf{HPOS E0 HBOR 300100 HDIR N HCON BWD}
	
	\textsf{TPOS E2500 N7000 U1000 TDIR S TBOR 300100 TCON BWD NEW WELD SEL CONN 
		TO PH AND P0 IS U}
	
	\textsf{SPRE /BOXI.SPEC/W300X100 LSTU /BOXI.SPEC/D300X100 ORIF TRUE POSF 
		TRUE}
	
	\textsf{NEW ELBO SEL WI STYP V THRO N5000 DIR U}
	
	\textsf{NEW ELBO SEL WI STYP H THRO U1000 DIR E}
	
	\textsf{NEW ELBO SEL WI STYP V THRO PT DIR N}
	
	\textsf{NEW WELD SEL CONN TO PT AND P0 IS E END}
	
	Note that it is assumed that a COCO element allowing BWD to BWD connections 
	already exists in your database.
	
	\begin{enumerate}
		\item VANTAGE PDMS PARAGON
	\end{enumerate}
	
	\subsection{Summary of Element Types}
	\label{subsec:summary}
	This appendix contains a glossary of the element types which you can use in 
	PARAGON, and a list of them grouped according to their function. Some 
	element types can be created and deleted in PARAGON, and have their standard 
	attributes of NAME and LOCK changed, but must have their particular 
	attributes set by other PDMS modules. These are indicated by references to 
	the appropriate manuals.
	
	The list of element types is the list of `special nouns' for PARAGON (its 
	\textsf{\textless snoun\textgreater }syntax diagram).
	
	\subsection{Glossary}
	For each element type, this glossary gives
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{48pt}|l|l|}
				\hline
				\textbf{Short Name}& 
				\textbf{Full Name}& 
				\textbf{Description} \\
				\hline
				ATLI& 
				ATLIst& 
				Attribute List \\
				\hline
				BLIS& 
				BLISt& 
				Bolt List \\
				\hline
				BLTA& 
				BLTAble& 
				Bolt Table \\
				\hline
				BOXI& 
				BOXIng& 
				Boxing (3D Geomset primitive) \\
				\hline
				CATE& 
				CATEgory& 
				Piping Category \\
				\hline
				CATA& 
				CATAlogue& 
				Catalogue DB \\
				\hline
				CCTA& 
				CCTAble& 
				Connection Compatibility Table \\
				\hline
				COCO& 
				COCO& 
				Connection Compatibility Element \\
				\hline
			\end{tabular}
			\label{tab21}
		\end{center}
	\end{table}
	
	\begin{itemize}
		\item the short name (four characters) as it is displayed on the screen
		\item the full name: the minimum abbreviation which can be used in a command is shown in uppercase
		\item a brief description
	\end{itemize}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{48pt}|l|l|}
				\hline
				\textbf{Short Name}& 
				\textbf{Full Name}& 
				\textbf{Description} \\
				\hline
				COMP& 
				COMPonent& 
				Piping Component \\
				\hline
				DATA& 
				DATA& 
				Data \\
				\hline
				DTAB& 
				DTABle& 
				Diameter Table \\
				\hline
				DTEX& 
				DTEXt& 
				Detailing Text \\
				\hline
				DTSE& 
				DTSEt& 
				Dataset \\
				\hline
				FITT& 
				FITTing& 
				Fitting Component \\
				\hline
				GMSE& 
				GMSEt& 
				3D Geomset \\
				\hline
				GMSS& 
				GMSSet& 
				Structural Ge \\
				\hline
				GPWL& 
				GPWL& 
				Group World \\
				\hline
				GROU& 
				GROUp& 
				Group \\
				\hline
				JOIN& 
				JOINt& 
				Joint Component \\
				\hline
				LCYL& 
				LCYLinder& 
				Cylinder (3D Geomset primitive) \\
				\hline
				LINE& 
				LINEs& 
				Line (3D Geomset primitive) \\
				\hline
				LPYR& 
				LPYRamid& 
				Pyramid (3D Geomset primitive) \\
				\hline
				LSNO& 
				LSNOut& 
				Snout (3D Geomset primitive) \\
				\hline
				LTAB& 
				LTABle& 
				Length Table \\
				\hline
				MSET& 
				MSET& 
				Measurement Set \\
				\hline
				MTEX& 
				MTEXt& 
				Material Text \\
				\hline
				MTYP& 
				MTYPe& 
				Measurement Type \\
				\hline
				NGMS& 
				NGMSet& 
				Negative 3D Geomset \\
				\hline
				NLCY& 
				NLCYlinder& 
				Negative Cylinder (Negative 3D Geomset primitive) \\
				\hline
				NLPY& 
				NLPYramid& 
				Negative Pyramid (Negative 3D Geomset primitive) \\
				\hline
				NLSN& 
				NLSNout& 
				Negative Snout (Negative 3D Geomset primitive) \\
				\hline
				NSBO& 
				NSBOx& 
				Negative Box (Negative 3D Geomset primitive) \\
				\hline
				NSCO& 
				NSCOne& 
				Negative Cone (Negative 3D Geomset primitive) \\
				\hline
				NSCT& 
				NSCTorus& 
				Negative Circular Torus (Negative 3D Geomset primitive) \\
				\hline
			\end{tabular}
			\label{tab22}
		\end{center}
	\end{table}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{48pt}|l|l|}
				\hline
				\textbf{Short Name}& 
				\textbf{Full Name}& 
				\textbf{Description} \\
				\hline
				NSCY& 
				NSCYlinder& 
				Negative Cylinder (Negative 3D Geomset primitive) \\
				\hline
				NSDS& 
				NSDSh& 
				Negative Dish (Negative 3D Geomset primitive) \\
				\hline
				NSEX& 
				NSEXtrusion& 
				Negative User-defined Extrusion (Negative 3D Geomset primitive) \\
				\hline
				NSRE& 
				NSREvolution& 
				Negative Solid of Revolution (Negative 3D Geomset primitive) \\
				\hline
				NSRT& 
				NSRTorus& 
				Negative Rectangular Torus (Negative 3D Geomset primitive) \\
				\hline
				NSSL& 
				NSSLcylinder& 
				Negative Slope-Bottomed Cylinder (Negative 3D Geomset primitive) \\
				\hline
				NSSP& 
				NSSPhere& 
				Negative Sphere (Negative 3D Geomset primitive) \\
				\hline
				NTUB& 
				NTUBe& 
				Negative Implied Tube (Negative 3D Geomset primitive) \\
				\hline
				PROF& 
				PROFile& 
				Profile Component \\
				\hline
				PTAX& 
				PTAXis& 
				Axial P-point \\
				\hline
				PTCA& 
				PTCAr& 
				Cartesian P-point \\
				\hline
				PLIN& 
				PLINe& 
				P-line \\
				\hline
				PTMI& 
				PTMIx& 
				Mixed Type P-point \\
				\hline
				PTSE& 
				PTSEt& 
				3D Pointset (with P-point member elements) \\
				\hline
				PTSS& 
				PTSSet& 
				Structural Pointset (with P-line member elements) \\
				\hline
				SANN& 
				SANNulus& 
				Structural Annulus (Structural Geomset primitive) \\
				\hline
				SBOL& 
				SBOLt& 
				Single Bolt (or Standard Bolt) Element \\
				\hline
				SBOX& 
				SBOX& 
				Box (3D Geomset primitive) \\
				\hline
				SCOM& 
				SCOMponent& 
				Piping Component \\
				\hline
				SCON& 
				SCONe& 
				Cone (3D Geomset primitive) \\
				\hline
				SCTO& 
				SCTOrus& 
				Circular Torus (3D Geomset primitive) \\
				\hline
				SCYL& 
				SCYLinder& 
				Cylinder (3D Geomset primitive) \\
				\hline
				SDIS& 
				SDISc/SDISk& 
				Disc (3D Geomset primitive) \\
				\hline
				SDSH& 
				SDSH& 
				Dish (3D Geomset primitive) \\
				\hline
			\end{tabular}
			\label{tab23}
		\end{center}
	\end{table}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{48pt}|l|l|}
				\hline
				\textbf{Short Name}& 
				\textbf{Full Name}& 
				\textbf{Description} \\
				\hline
				SDTE& 
				SDTExt& 
				Detailing Text \\
				\hline
				SECT& 
				SECTion& 
				Piping Section \\
				\hline
				SELE& 
				SELEc& 
				Selector - see the SPECON Reference Guide. \\
				\hline
				SEXT& 
				SEXTrusion& 
				User-defined Extrusion (3D Geomset primitive) \\
				\hline
				SFIT& 
				SFITting& 
				Fitting Component \\
				\hline
				SJOI& 
				SJOInt& 
				Joint Component \\
				\hline
				SLOO& 
				SLOOp& 
				Structural Loop (3D Geomset primitive) \\
				\hline
				SMTE& 
				SMTExt& 
				Material Text \\
				\hline
				SPRF& 
				SPRFile& 
				Profile Component \\
				\hline
				SPWL& 
				SPWL& 
				Specification World - see the SPECON Reference Guide. \\
				\hline
				SPCO& 
				SPCOm& 
				Specification Component - see the SPECON Reference Guide. \\
				\hline
				SPRO& 
				SPROfile& 
				Structural Profile (Structural Geomset primitive) \\
				\hline
				SPEC& 
				SPECi& 
				Specification - see the SPECON Reference Guide. \\
				\hline
				SPVE& 
				SPVErtex& 
				Structural Profile Vertex (Structural Geomset primitive) \\
				\hline
				SREC& 
				SRECtangle& 
				Structural Rectangle (Structural Geomset primitive) \\
				\hline
				SREV& 
				SREVolution& 
				Solid of Revolution (3D Geomset primitive) \\
				\hline
				SRTO& 
				SRTOrus& 
				Rectangular Torus (3D Geomset primitive) \\
				\hline
				SSLC& 
				SSLCylinder& 
				Slope-Bottomed Cylinder (3D Geomset primitive) \\
				\hline
				SSPH& 
				SSPHere& 
				Sphere (3D Geomset primitive) \\
				\hline
				STCA& 
				STCAtegory& 
				Structural Category \\
				\hline
				STSE& 
				STSEction& 
				Structural Section \\
				\hline
				SVER& 
				SVERtex& 
				Structural Vertex (3D Geomset primitive) \\
				\hline
				TEXT& 
				TEXT& 
				Text \\
				\hline
				TUBE& 
				TUBE& 
				Implied Tube (3D Geomset primitive) \\
				\hline
				UDEF& 
				UDEFinition& 
				Units Definition \\
				\hline
				UNIT& 
				UNIT& 
				Unit Element \\
				\hline
				USEC& 
				USECtion& 
				Unit Section \\
				\hline
			\end{tabular}
			\label{tab24}
		\end{center}
	\end{table}
	
	\subsection{Functional Groups}
	\label{subsubsec:functional}
	\textbf{3D Pointset elements:}
	
	\textsf{PTSEt PTAXi PTCAr PTMIx}
	
	\textbf{Structural Pointset elements:}
	
	\textsf{PTSSet PLINe}
	
	\textbf{3D Geomset elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|l|l|}
				\hline
				\textsf{GMSEt}& 
				\textsf{SBOX}& 
				\textsf{SDISc}& 
				\textsf{SDISk}& 
				\textsf{SCONe} \\
				\hline
				\textsf{LSNOut}& 
				\textsf{SDSH}& 
				\textsf{BOXIng}& 
				\textsf{SSLCylinder}& 
				\textsf{SSPHere} \\
				\hline
				\textsf{LCYLinder}& 
				\textsf{SCYLinder}& 
				\textsf{LINEs}& 
				\textsf{SCTOrus}& 
				\textsf{SRTOrus} \\
				\hline
				\textsf{TUBE}& 
				\textsf{LPYRamid}& 
				\textsf{SEXTrusion}& 
				\textsf{SREVolution}& 
				\textsf{SLOOp} \\
				\hline
				\textsf{SVERtex}& 
				& 
				& 
				& 
				\\
				\hline
			\end{tabular}
			\label{tab25}
		\end{center}
	\end{table}
	
	\textbf{Negative 3D Geomset elements:}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|l|l|l|l|l|}
				\hline
				\textsf{NGMSEt}& 
				\textsf{NSBOx}& 
				\textsf{NSCOne}& 
				\textsf{NLSNout}& 
				\textsf{NSDSh} \\
				\hline
				\textsf{NSSLcylinder}& 
				\textsf{NSSPhere}& 
				\textsf{NLCYlinder}& 
				\textsf{NSCYlinder}& 
				\textsf{NSCTorus} \\
				\hline
				\textsf{NSRTorus}& 
				\textsf{NLPYramid}& 
				\textsf{NSEXtrusion}& 
				\textsf{NSREvolution}& 
				\textsf{SLOOp} \\
				\hline
				\textsf{SVERtex}& 
				& 
				& 
				& 
				\\
				\hline
			\end{tabular}
			\label{tab26}
		\end{center}
	\end{table}
	
	\textbf{Structural Geomset elements:}
	
	\textsf{GMSSet SRECtangle SANNulus SPROfile SPVErtex}
	
	\textbf{Dataset elements:}
	
	\textsf{DTSEt DATA}
	
	\textbf{Piping Components:}
	
	\textsf{SCOMponent COMPonent }\textsf{\textit{number}}
	
	\textbf{Profile Components:}
	
	\textsf{SPRFile PROFile }\textsf{\textit{number}}
	
	\textbf{Joint Components:}
	
	\textsf{SJOInt JOINt }\textsf{\textit{number}}
	
	\textbf{Fitting Components:}
	
	\textsf{SFITting }(\textbf{NOT }\textsf{FITTing 
	}\textsf{\textit{number}}\textsf{)}
	
	\textbf{Material Text elements:}
	
	\textsf{SMTExt MTEXt }\textsf{\textit{number}}
	
	\textbf{Detailing Text elements:}
	
	\textsf{SDTExt DTEXt }\textsf{\textit{number}}
	
	\textbf{Group World elements:}
	
	\textsf{GPWL GROUp}
	
	\textbf{Specification World elements }(see the \textit{SPECON Reference Guide})\textbf{:}
	
	\textsf{SPWL SPECi SELEc SPCOm}
	
	\textbf{Catalogue administrative elements:}
	
	\textsf{CATAlogue SECTion STSEction CATEgory STCAtegory TEXT}
	
	\begin{table}[htbp]
		\begin{center}
			\begin{tabular}{|p{107pt}|p{73pt}|p{83pt}|p{86pt}|p{75pt}|}
				\hline
				\multicolumn{5}{|p{426pt}|}{\textbf{Bolt Table elements:}} \\
				\hline
				\textsf{BLTAble} \par \textsf{MBLIst}& 
				\textsf{BLISt} \par \textsf{DTABle}& 
				\textsf{SBOLt}& 
				\textsf{LTABle}& 
				\textsf{MBOLt} \\
				\hline
				\multicolumn{5}{|p{426pt}|}{\textbf{Connection Table elements:}} \\
				\hline
				\textsf{CCTAble}& 
				\textsf{COCO}& 
				& 
				\multicolumn{2}{|p{162pt}|}{} \\
				\hline
				\textbf{Units elements:} \par \textsf{UNIT} \par \textsf{UDEFinition}& 
				\textsf{MSET}& 
				\textsf{MTYP}& 
				\multicolumn{2}{|p{162pt}|}{\textsf{ATLIst USECtion}} \\
				\hline
			\end{tabular}
			\label{tab27}
		\end{center}
	\end{table}
	
	\textbf{.}
	
	\textbf{Index}
	
	ABREV, 9-5
	
	ACTIVE, 3-5
	
	ADEN, 9-6
	
	AIDS, 3-5
	
	ALARM, 3-4
	
	ALPHA, 3-3
	
	ALPHA FILE, 3-3
	
	ALPHA LOG, 3-3
	
	APARAM, 4-9, 8-4
	
	ATLI, 9-5
	
	BLIS, 9-3
	
	BLTA, 9-3
	
	BLTP, 9-3
	
	BOXI, 7-8
	
	BTSE, 9-3
	
	CATA, 4-4
	
	Catalogue, 4-4
	
	Catalogue Element Types, 2-5 CATE, 4-4
	
	Category, 4-4
	
	CCTA, 9-2, 4
	
	CE, 3-5, 5-2, 6-1 CENTRELINE. See CL CL, 6-6, 6-20
	
	COCO, 9-2, 4
	
	COLOUR, 3-5
	
	comma, 2-4
	
	COMP, 4-6, 4-12
	
	Cursor-picking Identifier, 2-4, 2-7
	
	DATA, 10-1
	
	DDANGLE, 6-1, 6-17, 8-13, 8-18
	
	DDHEIGHT, 6-1, 6-17
	
	DDRADIUS, 6-1, 6-17
	
	DECP, 9-6
	
	DES APARAM, 4-10
	
	DES OPARAM, 4-10
	
	DES PARAM, 4-10
	
	Dimensions, 2-5
	
	DTAB, 9-4
	
	DTEX, 4-6
	
	DTSET, 4-6, 10-1
	
	END, 5-2, 5-3
	
	Expressions, 2-5
	
	filename, 2-4
	
	FINISH, 3-2
	
	FIRST, 5-3
	
	FITT, 4-7, 4-14
	
	GETWORK, 3-2
	
	GMSET, 4-6, 7-6, 8-19
	
	GMSSET, 4-7, 7-26, 8-22
	
	GOTO, 5-3
	
	INCBOR, 9-9
	
	INSTALL, 3-1
	
	INSULATION, 6-23
	
	integer, 2-3
	
	IPARAM, 4-8, 8-4
	
	JOIN, 4-7, 4-13
	
	LAST, 5-3
	
	LCYL, 7-11
	
	LENGTH, 6-24, 6-25
	
	letter, 2-3
	
	LEVEL, 6-6, 6-22
	
	LINE, 7-16
	
	LPYR, 7-17
	
	LSNO, 7-20
	
	LTAB, 9-4
	
	MEMBER, 5-3
	
	minus, 2-4
	
	MMBOR, 9-9
	
	MODEL, 6-1, 6-17
	
	MSET, 9-5
	
	MTEX, 4-6
	
	MTYP, 9-5
	
	MULT, 9-5
	
	NA, 8-17
	
	name, 2-4
	
	NEW, 8-2
	
	NEXT, 5-3
	
	NGMSET, 4-6, 7-25
	
	NOMINB, 9-9
	
	NRBWLD, 9-9
	
	NUMBER, 8-15
	
	NUMBERS, 6-24
	
	OBST, 7-7, 7-27
	
	OBSTRUCTION, 6-6, 6-23
	
	OPARAM, 4-9
	
	OWNER, 5-2
	
	PAAX, 8-23
	
	PARAGON, 3-1
	
	PARAM, 4-8, 8-4
	
	PAXI, 8-23
	
	PBORE, 8-15
	
	PCON, 1, 4
	
	PCONNECTION, 8-15
	
	PDISTANCE, 8-14
	
	PKEY, 6-25, 8-17, 8-19
	
	PLAXI, 8-18
	
	PLINE, 7-4, 8-17
	
	PLINES, 6-4, 6-25
	
	plus, 2-4
	
	PPOINT, 7-1, 8-10, 8-11, 8-12
	
	PPOINTS, 6-2, 6-24
	
	PREVIOUS, 5-3
	
	PROF, 4-7, 4-13
	
	PROFILE, 6-21
	
	PSKEY, 8-16
	
	PTAXI, 7-2, 8-10, 8-13
	
	PTCAR, 7-3, 8-11
	
	PTCDIRECTION, 8-15
	
	PTMIX, 7-3, 8-12
	
	PTSET, 4-6, 7-1, 8-10
	
	PTSSET, 4-6, 7-4, 8-17
	
	PURP, 9-9
	
	PX, 8-15, 8-19
	
	PY, 8-15, 8-19
	
	PZ, 8-15
	
	QUERY, 8-3
	
	QUIT, 3-2
	
	RECREATE, 3-1
	
	REPRESENTATION, 6-2, 6-4, 6-6, 6-20, 6-
	
	21, 6-22, 6-23, 6-24, 6-25
	
	SAME, 5-2
	
	SANN, 7-29, 8-22
	
	SAVEWORK, 3-2
	
	SBOL, 9-4
	
	SBOX, 7-8
	
	SCOM. See COMP SCON, 7-10
	
	SCTO, 7-18
	
	SCYL, 7-12
	
	SDIS, 7-14
	
	SDSH, 7-15
	
	SDTE, 9-1. See DTEX
	
	\begin{flushright}
		\textit{Index}
	\end{flushright}
	
	SECT, 4-4
	
	Section, 4-4
	
	SETTINGS, 6-1, 6-17
	
	SEXT, 7-23 SFIT. See FITT SIGF, 9-6
	
	SJOI. See JOIN SKEY, 8-16
	
	SLOO, 7-23, 7-24 SMTE, 9-2. See MTEX
	
	solid, 2-4
	
	space, 2-4
	
	Specific Element Identifier, 2-7 SPRF. See PROF
	
	SPRO, 7-30
	
	SPVE, 7-30
	
	SREC, 7-28, 8-22
	
	SREV, 7-24
	
	SRTO, 7-19
	
	SSLC, 7-13
	
	SSPH, 7-21
	
	star, 2-4
	
	STCA, 4-4
	
	STSEC, 4-4
	
	SVER, 7-23, 7-24
	
	Syntax diagram conventions, 2-1 text, 2-4
	
	TEXT, 4-7, 9-8
	
	TRACE, 3-4
	
	TUBE, 6-6, 6-20, 7-22
	
	TYPE, 5-3
	
	UDEF, 9-5
	
	UNIT, 9-5
	
	UNITS, 9-6
	
	USEC, 9-5
	
	User-defined Nominal Dimensions, 9-8 value, 2-3
	
	varid, 2-4
	
	VISIBLE, 3-5
	
	word, 2-3
	
	\begin{thebibliography}{99}
		\bibitem{zhuyiwencyq} ?,??, and ?,???. (?), \textit{abaqus??????}.,????????, ??,(2003).
		\bibitem{ligb} ?,??, and ?. (?), \textit{PDMS PROPCON ???????11.6????}.,????????????, ??,(2018).
		
		
	\end{thebibliography}
	
	%\end{multicols}
\end{document}
